InformAction Forums

fx3.6.3, ns1.9.9.87, new profile, forbid noscript.net, load http://noscript.net/feed

Is the feed view a chrome child doc of the original xml doc? Then I guess this makes sense, still an exception should be made for chrome.

also a minor issue, "Invalid chrome URI: /" message is logged when the NS menu is opened, what does it mean?

al_9x wrote:Is the feed view a chrome child doc of the original xml doc? Then I guess this makes sense, still an exception should be made for chrome.

Nothing to do about it. The cascading permissions behavior is a Gecko docShells built-in, so you can expect unfixable corner edges and this is one of the reasons this option is not user-facing.

also a minor issue, "Invalid chrome URI: /" message is logged when the NS menu is opened, what does it mean?

No idea, it's not a message from NoScript. Probably something somewhere didn't expect the chrome page to be loaded in a scriptless docShell.