Page 1 of 1
World Golf Tour Javascript problem
Posted: Wed Nov 23, 2011 2:52 pm
by sumo55
Having problems getting a a javascript to run in Fx while in NS. I go to a specific World Golf Tour (wgt.com/courses/) page and when I hover over a link there I get "javascript:;" and clicking does nothing. The site url is whitelisted and I've tried temporarily enabling the page but still nothing. Javascript is enabled in my Fx Preferences and when I use Safari it works fine. Suggestions what to change? I've tried enabling all of the additional permissions for trusted sites in the NS Options but nothing works there either...
Re: World Golf Tour Javascript problem
Posted: Wed Nov 23, 2011 5:25 pm
by therube
Looks like google-analytics.com is also needed.
Re: World Golf Tour Javascript problem
Posted: Wed Nov 23, 2011 11:55 pm
by sumo55
That was it. I had marked google-analytics "untrusted." Thanks!
Re: World Golf Tour Javascript problem
Posted: Thu Nov 24, 2011 1:08 am
by Tom T.
therube wrote:Looks like google-analytics.com is also needed.
Shouldn't ever be necessary. By default, NS runs a
Surrogate Script for G-A.com, which makes the page happy while protecting your privacy.
I just went there, TA'd the site's sole script source (wgt.com), hovered over a link link

, and it worked fine.
I did *not* allow media5 or doubleclick.
Will recheck on Fx 8.0, but the surrogate should rule out g-a as being the source of the issue.
Re: World Golf Tour Javascript problem
Posted: Thu Nov 24, 2011 1:34 am
by Tom T.
Wow, on Fx 8.0 it works even with *all* scripting blocked. Will retry on F3.
Couldn't find any <noscript> elements in the page source (to provide either graceful fallback or the usual warning, "Must enable Javascript", etc.)
Can you please go there, open Firefox Tools > Web Developer > Error Console, click red "Errors", and copy/paste all of them here? Also, click blue "Messages", look for any [NOSCRIPT], [ABE], or related messages, and post those here also?
[O/T rant] Why on Earth did they have to make the Error Console less accessible and less visible? It isn't just a "Web Developer" tool; it's vital for all troubleshooting. What was wrong with leaving it directly on the Tools menu? ... another reason I stick with Fx 3.6.x. [/rant]