Re: Current 'release' versions of Firefox & NoScript
THIS WEBSITE
Is a phone book directory provided via Frontier for various areas all around the USA. The page I've linked above (and any other specific locale one could select) has but one domain to "allow scripts", namely "dexpages.com". With this scrip allowed (and the icon a plain S set in a white background indicating there are no scrips being blocked) the page will not load and instead displays only a logo in the center of a blank white page. Allowing all scrips globally also has no effect and creates the same results. Disabling NoScript completely in the addons section of Firefox eliminates the problem and the page can be viewed normally. All other addons have been eliminated, beginning with disabling all, then re-enabling one at a time. NoScript was the final addon to be enabled and the site no longer loaded. To verify, I disabled and re-enabled NoScript several times, each with the same result. All settings in the options are default. I disabled each option in turn and rechecked the page --re-enabling each option with each ineffectual result-- and after all were tried I'm at a loss as to what might be blocking the page within NoScript. I don't believe this is a NoScript 'bug' or 'failure', but rather that I'm just missing some easy fix that I've overlooked. Neither the FAQ's, nor a thorough search of all existing forum posts here resulted in solution to this very specific problem. Any help will be greatly appreciated.
Thanks in advance.
ga surrogate failure
-
- Posts: 3
- Joined: Sun Aug 28, 2016 11:53 pm
ga surrogate failure
Last edited by barbaz on Mon Aug 29, 2016 3:39 am, edited 1 time in total.
Reason: clearer topic title
Reason: clearer topic title
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
Re: Please Help: Site Broken

When this issue occurs, do you see anything related in the Browser Console? (Ctrl-Shift-J)
(if you don't know what's related, turn off CSS warnings and post everything else you see)
*Always* check the changelogs BEFORE updating that important software!
-
-
- Posts: 3
- Joined: Sun Aug 28, 2016 11:53 pm
Re: Please Help: Site Broken
With Cascading Style Sheets off, only the following appears in the js tab (all other tabs are blank)
Use of getAttributeNode() is deprecated. Use getAttribute() instead.jscript.js:86:565
SecurityError: The operation is insecure.policy.js:303
Warning: 'nsIOService::NewChannel()' deprecated, please use 'nsIOService::NewChannel2()'script-compiler.js:22:13
Use of Mutation Events is deprecated. Use MutationObserver instead.RemoteAddonsParent.jsm:787
Use of getPreventDefault() is deprecated. Use defaultPrevented instead.jquery.js:55:817
Warning: NetUtil.asyncFetch() requires the channel to have one of the security flags set in the loadinfo (see nsILoadInfo). Please create channel using NetUtil.newChannel()
I cleared out everything, opened only the offending site, and pasted it above so the data would be exclusive and untainted.
Thanks for responding so quickly.
Use of getAttributeNode() is deprecated. Use getAttribute() instead.jscript.js:86:565
SecurityError: The operation is insecure.policy.js:303
Warning: 'nsIOService::NewChannel()' deprecated, please use 'nsIOService::NewChannel2()'script-compiler.js:22:13
Use of Mutation Events is deprecated. Use MutationObserver instead.RemoteAddonsParent.jsm:787
Use of getPreventDefault() is deprecated. Use defaultPrevented instead.jquery.js:55:817
Warning: NetUtil.asyncFetch() requires the channel to have one of the security flags set in the loadinfo (see nsILoadInfo). Please create channel using NetUtil.newChannel()
I cleared out everything, opened only the offending site, and pasted it above so the data would be exclusive and untainted.
Thanks for responding so quickly.
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
Re: Please Help: Site Broken
Confirmed the issue on my end... almost. I get the option to Allow google-analytics.com in NoScript, and with that, the site works.
However, you should never need to Allow google-analytics only in order to get a site to work, as there is surrogate script for it. So this is a NoScript bug, but I don't have time to investigate this further, sorry.
Moving to NoScript Surrogates and making clearer title. Thanks for the report
However, you should never need to Allow google-analytics only in order to get a site to work, as there is surrogate script for it. So this is a NoScript bug, but I don't have time to investigate this further, sorry.
Moving to NoScript Surrogates and making clearer title. Thanks for the report
*Always* check the changelogs BEFORE updating that important software!
-
-
- Posts: 3
- Joined: Sun Aug 28, 2016 11:53 pm
Re: ga surrogate failure
Confirmed here as well. Google-analytics was not appearing in NoScript originally, but after allowing it through Ghostery 5.4.11, Adblock Plus and Request Policy it became available in the NoScript interface. Once temporarily allowed in NoScript, the Dexpages site functioned normally.
I will await a surrogate script tweak or an official update that will fix this NoScript bug.
Thanks for all your kind help.
Many thanks to the developers and all others who contribute to this excellent addon. I find it to be essential.
I will await a surrogate script tweak or an official update that will fix this NoScript bug.
Thanks for all your kind help.
Many thanks to the developers and all others who contribute to this excellent addon. I find it to be essential.
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:48.0) Gecko/20100101 Firefox/48.0
Re: ga surrogate failure
Finally I had the chance to try to look into this.
If bork or remove the ga surrogate, the page works. Hangs the browser a short while, but seemingly works.
You're supposed to be able to create a .exceptions pref for the surrogate to not apply, but it doesn't have any effect for me, so never mind that i guess
Seemingly anything I do to the surrogate has no effect, except adding a console.log call at the very beginning.
Looked at some of the page's ga-related scripts but I couldn't gain any insight from it.
Running out of ideas fast..
If bork or remove the ga surrogate, the page works. Hangs the browser a short while, but seemingly works.
You're supposed to be able to create a .exceptions pref for the surrogate to not apply, but it doesn't have any effect for me, so never mind that i guess

Seemingly anything I do to the surrogate has no effect, except adding a console.log call at the very beginning.

Looked at some of the page's ga-related scripts but I couldn't gain any insight from it.
Running out of ideas fast..
*Always* check the changelogs BEFORE updating that important software!
-