Facebook sets the value of <spellchecker.dictionary> to <ru_RU> every time I start entering text (language doesn't matter) in a textbox on FB
Facebook sets the value of <spellchecker.dictionary> to <ru_RU> every time I start entering text (language doesn't matter) in a textbox on FB.
FF: Firefox 20.0 - Mozilla Firefox for Linux Mint OS: Linux Mint 13
I haven't noticed any other website I use causing that problem: all of them use the predefined (in prefs.js) value of <spellchecker.dictionary> and don't change it unless I change the speller language manually. The only way I can change the value of <spellchecker.dictionary> back to <en_US> is manually choosing English in context menu of a textbox, or editing "prefs.js", every time Facebook messes it up.
Why does FB always sets <spellchecker.dictionary> to <ru_RU>???
My default locale is "en-US": <general.useragent.locale> = "en-US".
Please help.
Okulungisiwe
All Replies (3)
Websites should not be able to change a pref setting.
Only an extension can do this.
Start Firefox in Safe Mode to check if one of the extensions (Firefox/Tools > Add-ons > Extensions) or if hardware acceleration is causing the problem (switch to the DEFAULT theme: Firefox/Tools > Add-ons > Appearance).
- Do NOT click the Reset button on the Safe Mode start window or otherwise make changes.
- https://support.mozilla.org/kb/Safe+Mode
- https://support.mozilla.org/kb/Troubleshooting+extensions+and+themes
What is the order of the installed languages?
You can check the order of the installed Languages.
- Tools > Options > Content > Languages
Hi cor-el, thanks for advice.
Seems like my Firefox extension "United States English Spellchecker" may have caused that behavior. I disabled it, restarted FF, and -- the problem is gone! Moreover, when I enabled it again, the problem didn't come back, which raises some questions... About installed languages. The thing is, my OS (Linux Mint) has a few preinstalled system-wide spellcheckers, which are also active in FF, in addition to FF own extension spellchecker en_US, which may have complicated the situation. Or, it may be just an extension bug, who knows...
Anyway, thank you a lot! That problem has been bothering me for a while.
You're welcome