Any issues using autoconfig, lockPref, CAPS?

[ItsColdOut]

Hi folks. I'm experimenting with a defaults/preferences/autoconfig.js:

pref("general.config.obscure_value", 0);
pref("general.config.filename", "FirefoxCfg.js");

approach to setting up Firefox 16.0.2. Within FirefoxCfg.js I'm using LockPref to set everything the way I want it. I'm considering the potential benefits of CAPS and at present have two test entries:

lockPref("capability.policy.default.Window.postMessage.get", "sameOrigin");
lockPref("capability.policy.default.XMLHttpRequest.open", "sameOrigin");

but I'm still trying to think CAPS usage through. So far I haven't noticed this approach interfering with NoScript's operation but I thought I better check with you guys to see if the use of lockPref, particularly the lockPrefing of a CAPS entry, might cause problems for NoScript. Is anyone doing this? Comments? Thanks in advance.

[Giorgio Maone]

Yes, using CAPS interferes with NoScript and there's no easy work-around.
Notice also that since the only significant CAPS client to-date is NoScript, CAPS feature which are not required by NoScript operation are being slowly removed from the Mozilla code base.