Hecate
04-03-2010, 12:25
I've recently updated to Firefox 3.5.8 on Windows 7. I have British English Dictionary 1.19 add-on installed.
Each time I start up my computer and open Firefox, I notice that the spellcheck isn't working. When I check Tools>Add-ons, I'm informed that British English Dictionary 1.19 isn't compatible with this version of Firefox. I click the 'Find updates' button, and the dictionary add-on is duly updated. Spellcheck goes on to work as it should.
All is well until the next time I close down and restart the computer, when Firefox again tells me that British English Dictionary 1.19 isn't compatible, the spellcheck fails to work, and the cycle begins again.
It isn't that the dictionary add-on isn't working at all, or that an update isn't being applied - it's that each time the computer is closed down, Firefox seems to forget that it's had an update applied to the British English dictionary add-on.
I do clear cookies etc using CCleaner each time I close down the computer. I've done that for ages though, and this problem has only appeared in the last couple of weeks since I upgraded to Firefox 3.5.8.
Any ideas what's going on?
Each time I start up my computer and open Firefox, I notice that the spellcheck isn't working. When I check Tools>Add-ons, I'm informed that British English Dictionary 1.19 isn't compatible with this version of Firefox. I click the 'Find updates' button, and the dictionary add-on is duly updated. Spellcheck goes on to work as it should.
All is well until the next time I close down and restart the computer, when Firefox again tells me that British English Dictionary 1.19 isn't compatible, the spellcheck fails to work, and the cycle begins again.
It isn't that the dictionary add-on isn't working at all, or that an update isn't being applied - it's that each time the computer is closed down, Firefox seems to forget that it's had an update applied to the British English dictionary add-on.
I do clear cookies etc using CCleaner each time I close down the computer. I've done that for ages though, and this problem has only appeared in the last couple of weeks since I upgraded to Firefox 3.5.8.
Any ideas what's going on?