NoScript blocking chrome:// (can't add exception)

knikk · Post by **knikk** » Wed Dec 21, 2011 12:58 pm

Hi,

NoScript blocks JavaScript in chrome://-URIs, but adding an exception doesn't work. When I click on on "Allow chrome:" in the menu the page will reload, but chrome: will be forbidden again. When I try to add it in the Options window the Allow will be greyed out.

I want to allow it for epubreader extensions, which appears to have some tiny glitches because of it.

Post by **Tom T.** » Fri Dec 30, 2011 4:20 am

Sorry that this one hasn't been answered in more than a week. I'll flag it for Giorgio's personal attention.

Thank you for your patience.

Post by **Giorgio Maone** » Mon Jan 02, 2012 11:10 pm

JavaScript execution on chrome: URIs cannot be disabled anyway because they're privileged, so the real bug here is them appearing to be allowable.
I'll try to look into the epubreader-specific issue as soon as possible, anyway.

beyondo · Post by **beyondo** » Tue Jul 03, 2012 3:23 pm

Looks like this one is still reproducible.

I get the red circle when I open a document with epubreader. Clicking "allow chrome:" makes it go away for a second, but then it quickly comes back.

Text says "Scripts Partially Allowed, 1/2 (file://) | <SCRIPT>: 2 | <OBJECT>: 0

Post by **therube** » Tue Jul 03, 2012 4:26 pm

Seemingly it should not be affecting anything whether able to be "allowed" or if it were grayed out?

AMO: EPUBReader

This looks to be working just fine, http://epub-samples.googlecode.com/file ... 20322.epub

Code: Select all

chrome://epubreader/content/reader.xul?id=1

drm200 · Post by **drm200** » Fri Jul 20, 2012 3:44 pm

I have exactly the same problem described above.

NoScript blocks JavaScript in chrome://-URIs, but adding an exception doesn't work. When I click on on "Allow chrome:" in the menu the page will reload, but chrome: will be forbidden again. When I try to add it in the Options window the Allow will be greyed out (and can not be edited). I am using the latest noscript version and firefox 14.01

Post by **therube** » Fri Jul 20, 2012 7:37 pm

And what chrome:// URI are you running up against?

If you disable NoScript & restart, does the chrome:// problem persist?

Questioner · Post by **Questioner** » Thu Jan 24, 2013 11:16 am

therube, where can I put that code snippet? Please explain.

therube wrote:Seemingly it should not be affecting anything whether able to be "allowed" or if it were grayed out?

AMO: EPUBReader

This looks to be working just fine, http://epub-samples.googlecode.com/file ... 20322.epub
Code: Select all
chrome://epubreader/content/reader.xul?id=1

InformAction Forums

NoScript blocking chrome:// (can't add exception)

NoScript blocking chrome:// (can't add exception)

Re: NoScript blocking chrome:// (can't add exception)

Re: NoScript blocking chrome:// (can't add exception)

Re: NoScript blocking chrome:// (can't add exception)

Re: NoScript blocking chrome:// (can't add exception)

Re: NoScript blocking chrome:// (can't add exception)

Re: NoScript blocking chrome:// (can't add exception)

Re: NoScript blocking chrome:// (can't add exception)