The NYTimes has a feature where when you highlight a word in an article a "question mark" will appear above the word. Clicking on the "question mark" opens a new window with the word's definition. This works with Firefox 5.0 but something in Firefox 7.0 has broken the feature (it was working about a month ago). In FF7.0 the "question mark" still appears but clicking does nothing. Disabling Noscript restores the functionality.
I created a new profile and installed the latest NoScript development build (2.1.1.2rc8). No other extensions installed. With NoScript disabled the feature works. Enabling NoScript breaks the feature. I have tried setting "Disable scripts globally", disabling XSS and ABE with no effect. There are no NoScript messages in the error console.
NYTimes Word Lookup and Firefox 7.0
NYTimes Word Lookup and Firefox 7.0
Mozilla/5.0 (Windows NT 5.1; rv:7.0a1) Gecko/20110624 Firefox/7.0a1
- Giorgio Maone
- Site Admin
- Posts: 9454
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: NYTimes Word Lookup and Firefox 7.0
It's this Firefox bug.
To work-around, you can temporarily disable the popunder surrogate by setting the noscript.surrogate.popunder.sources about:config preference to an empty string.
To work-around, you can temporarily disable the popunder surrogate by setting the noscript.surrogate.popunder.sources about:config preference to an empty string.
Mozilla/5.0 (Windows NT 5.2; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Re: NYTimes Word Lookup and Firefox 7.0
Thanks Giorgio. Are you searching for the regression window?
Mozilla/5.0 (Windows NT 5.1; rv:7.0a1) Gecko/20110624 Firefox/7.0a1
- Giorgio Maone
- Site Admin
- Posts: 9454
- Joined: Wed Mar 18, 2009 11:22 pm
- Location: Palermo - Italy
- Contact:
Re: NYTimes Word Lookup and Firefox 7.0
I cannot ATM. Would you?Jim Too wrote:Thanks Giorgio. Are you searching for the regression window?
Mozilla/5.0 (Windows NT 5.2; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0
Re: NYTimes Word Lookup and Firefox 7.0
According to the thread they have now found the possible culprit.
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20100101 Firefox/5.0