Vanwege onderhoudswerkzaamheden die uw ervaring zouden moeten verbeteren, heeft deze website beperkte functionaliteit. Als een artikel uw probleem niet verhelpt en u een vraag wilt stellen, kan onze ondersteuningsgemeenschap u helpen in @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Inline spell checker partially functioning

  • 1 antwoord
  • 1 heeft dit probleem
  • 2 weergaven
  • Laatste antwoord van 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

Alle antwoorden (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.