This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

Inline spell checker partially functioning

  • 1 amsa
  • 1 yana da wannan matsala
  • 2 views
  • Amsa ta ƙarshe daga guigs

NEN14
NEN14
more options

Recently updated to TB 24.3.0. The inline spelling checker seems to be only partially working in V24. When composing, at random, it flags SOME misspellings, but not all of them. On the misspellings that is misses, if I go back and add a letter to the misspelled word and delete the same letter, then it will properly flag the misspelling. It seems to be a problem with the mechanism that keeps track of which words have been checked. I did not see this issue in TB versions prior to 24. I'm running XP 32bit SP3. Is this the proper place to report this bug?

Thanks for everyone's hard work on TB.

Niel

Recently updated to TB 24.3.0. The inline spelling checker seems to be only partially working in V24. When composing, at random, it flags SOME misspellings, but not all of them. On the misspellings that is misses, if I go back and add a letter to the misspelled word and delete the same letter, then it will properly flag the misspelling. It seems to be a problem with the mechanism that keeps track of which words have been checked. I did not see this issue in TB versions prior to 24. I'm running XP 32bit SP3. Is this the proper place to report this bug? Thanks for everyone's hard work on TB. Niel

All Replies (1)

guigs
guigs
more options

Hi NEN14, Niel,

Thank you for your question. Please email the developer of the add on to see if this is an issue that will be updated in the next update.

Add ons are supported by the developers and users who also use the add on may have a better answer for you. I apologize for the inconvenience.