NoScript causes problems with 1Password

[Tom T.]

...Never had any issues but now 1Password just stopped filling in my passwords UNLESS I enable javascript. At first I thought I must have done something wrong but after doing a web search it seems that 1Password has changed. It needs javascript enabled now.

Why????
"If it ain't broke, don't fix it." If 1Pass worked before, why did they have to introduce this complication? (Rhetorical question; seems the whole world is moving in this direction.)

just disable the rapid fire protection (set "noscript.clearClick.rapidFireCheck" to "false" in "about:config" in Firefox)

I have no idea what that means. But is it safe?

Not as safe as it was, or it wouldn't be there in the first place.

From what I read on the net and out of the publicly available answers of the 1Password staff, they can't or won't change anything.

Typical.

Could you maybe find a workaround/exception for 1Password in one of the next NoScript versions so the two of them will continue to work together?

I'm not familiar with 1Pass. Are the scripts identifiable as belonging to them? I. e., do they show up in the NoScript menu separately from the web site's scripting? ... probably not, but if they do, yes, it can work.

Otherwise, this Mac user found a better alternative. You might like to check that out.