| 1. |
Solve : Firefox 21.0 problem with iGoogle? |
|
Answer» I'm using Firefox 21.0 and I have my iGoogle page as my home page. Since about 24 hours ago, when I click on the Home button I get a page which I have seen described as a "Stock quote disclaimer". The url in the address bar is what I expect my home page to be, namely http://www.google.co.uk/ig Have you downloaded anything recently that might have had a subtle "I agree' greyed out section. Not that I know of. Quote Generally I would say to look at "Tools, Options, General" and reset the home page you desire. That setting never changed. I changed it myself from google.co.uk/ig to google.com/ig and the problem went away. If I change it back, the disclaimer is still there. Same problem with FF22?Quote from: Allan on June 27, 2013, 08:40:59 AM Same problem with FF22? Yes. I have just noticed that it occurs on both google.com/ig and google.co.uk/ig when the relevant domain is forbidden in NoScript and goes away when it is allowed. Strike that. It comes and goes! Quote I changed the url from google.co.uk/ig to google.com/ig and the home button takes me straight to my iGoogle page, no stock price disclaimer This is no longer true. Either one gets the disclaimer. If I monkey around with User Agent Switcher I can make it go away but, it seems, not for ever. What happens with launching safe mode Firefox from the Start Menu ? ? I suspect one or more broken extensions.Quote from: patio on June 27, 2013, 04:32:45 PM What happens with launching safe mode Firefox from the Start Menu ? ? Problem does not occur in safe mode; I tried disabling extensions one by one, no change until I went to disable NoScript (version 2.6.6.6) - it suggested that this was dangerous and suggested leaving it enabled and choosing "Disable script checking globally" instead. I did this and the problem went away. I re-enabled script checking globally and it came back. I noticed that when in the iGoogle page I have 3 sites available in the NoScript right click menu - google.com, gstatic.com, and googleusercontent.com. If I allow all 3 the problem seems (for now) to go away. So thanks, Patio, for pointing me in the right direction (I think). You're more than Welcome Salmon... There may be a newer update for NoScript as well... |
|