Very revealing. I stopped using NoScript a while ago since it would not properly whitelist some sites. At the time I was wondering why the plugin was updated so frequently with very similar change logs each time. This post explains why. Interfering with other extensions' internal state is simply unacceptable. Firefox should consider sandboxing the browser extensions. Maybe they'll get to that after they implement Chr…
>> "Interfering with other extensions' internal state is simply unacceptable" Interfering with other websites revenue models is also simply unacceptable by using adblock.
Nobody has a right to show me advertising, just as I don't have a right to read someone's content. If publishers have a problem with it they need to find a way to not display content to clients who are blocking ads.
But this isn't what we're talking about. We're talking about NoScript using my computer to interfere with other plugins. The behavior is unexpected and unwanted.
If the behavior is "ok" then the NoScript people shouldn't have any problem owning up to it, even broadcasting it to all their users. But I think we all know how that would play out.
It would be no different than if when you installed Firefox on your computer it made Safari break, or included some obscure option deep in its configuration menu like "[x] Break Safari."