Mozilla VPN is currently experiencing an outage. Our team is actively working to resolve the issue. Please check the status page for real-time updates. Thank you for your patience.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Spellchecker stopped working

  • 2 replies
  • 1 has this problem
  • 1 view
  • Last reply by cor-el

more options

I first noticed in in facebook, but spellchecker has stopped working across all sites in FF. Not MSIE or MS Word or Outlook.

This happened

Every time Firefox opened

== I misspellered a wurd

I first noticed in in facebook, but spellchecker has stopped working across all sites in FF. Not MSIE or MS Word or Outlook. == This happened == Every time Firefox opened == I misspellered a wurd

All Replies (2)

more options

You can see which dictionary is selected if you right-click in a text area and open the Languages submenu. Also make sure that [[X]"Check Spelling" in the right-click context menu has a tick. You can also try to toggle the "Check Spelling" item off and on again.

See http://kb.mozillazine.org/Spell_checking and How do I use the Firefox spell checker? See also http://kb.mozillazine.org/Dictionaries

Some have reported that toggling the "Check Spelling" check-mark in the right-click context menu works. .......... See also: Tools > Options > Advanced : General: Browsing: "Check my spelling as I type" http://kb.mozillazine.org/layout.spellcheckDefault http://kb.mozillazine.org/spellchecker.dictionary


Verify on the about:config page that the pref ui.SpellCheckerUnderlineStyle is not set to "0" See http://kb.mozillazine.org/ui.SpellCheckerUnderlineStyle

To open the about:config page, type about:config in the location (address) bar and press the Enter key, just like you type the url of a website to open a website. If you see a warning then you can confirm that you want to access that page.

more options

I have the same issue as described. This started when I installed FF 3.6.6 - FF 3.6.5 works fine. Is it possible issue with this version?