NoScript breaking/broken by CAPS?

[Guest]

I just learned about Firefox's CAPS feature and, well, it doesn't seem to play nice with NoScript.

I've added these prefs to my user.js:

Code: Select all

user_pref("capability.policy.noOpen.sites", "http://megaupload.com");
user_pref("capability.policy.noOpen.Window.open", "noAccess");
user_pref("capability.policy.policynames", "maonoscript, noOpen");

But, if NoScript is enabled, it breaks megaupload.com; i.e. no JavaScript is allowed to run at all, even though it is in my NS whitelist. Any idea what's causing this?

[Giorgio Maone]

NoScript is currently the main and more complex CAPS client, i.e. it uses CAPS intensively and is likely to break other usages or being broken by them.
It should also be noted that most of the CAPS functionality is planned to be removed in a future Firefox version, mainly for performance purposes, keeping only the bare bones to let NoScript work.

Notice also that most of the thing you could do with CAPS, you can emulate by using NoScript's script surrogates.

In your case, for instance,

Code: Select all

user_pref("noscript.surrogate.noOpen.sources", "@http://megaupload.com");
user_pref("noscript.surrogate.noOpen.replacement", "open=function(){}");