InformAction Forums

The latest 1Password extension stopped working when NoScript is enabled on the particular site. The 1Password developers and support said that a Mozilla framework requires JS, when I asked them and it seems unlikely that they would fix their product.
Is it possible that NoScript be modified so that it 1Password works on sites with JS disabled by NoScript. I know that this is not NoScript issue, but 1Password, but again -- they don't seem to be able or willing to fix it. I am not even sure if it can be fixed on the NoScript side.

Their support staff says in http://support.agilebits.com/discussion ... t_14328208

The JetPack extension APIs that Mozilla provides require JavaScript in order for 1Password to function.

Is that true, Giorgio, that having JavaScript enabled is a requirement of JetPack now?

Yes, perhaps Giorgio would know.

I'm having this same problem--I need to disable both Bitdefender and NS to get the latest 1Password extension to work (having said that I've recently updated Firefox, NS and 1P, so I'm not sure which one is to "blame", but I had been using both 1P and NS together for years until now).

Alan Baxter wrote:Is that true, Giorgio, that having JavaScript enabled is a requirement of JetPack now?

Nope.
Jetpack content scripts live in a sandbox, just like those used by NoScript's surrogates. If the above was true, surrogates wouldn't work either.

Oliver L. wrote:I'm having this same problem--I need to disable both Bitdefender and NS to get the latest 1Password extension to work (having said that I've recently updated Firefox, NS and 1P, so I'm not sure which one is to "blame", but I had been using both 1P and NS together for years until now).

In the 1password extension release notes they also mention "Updated Firefox extension to use Mozilla’s latest Add-on SDK." so it is 1P change.
If you check my thread at the 1password forum (link in my original post here) reverting back to previous version of 1password works.
You could try to ask the 1Password developers to fix it, but as you could see from that thread I gave up. I will be using the previous version while it works, but I am looking for another password manager in the meantime.

Giorgio Maone wrote:

Alan Baxter wrote:Is that true, Giorgio, that having JavaScript enabled is a requirement of JetPack now?

Nope.
Jetpack content scripts live in a sandbox, just like those used by NoScript's surrogates. If the above was true, surrogates wouldn't work either.

Giorgio -- Thanks a lot for the explanation. Keeping NoScript enabled as much as possible is important for me, so I am looking for compatible password managers.