Closed Bug 627483 Opened 15 years ago Closed 12 years ago

last two beta's (8 and 9) have seen an uptick in problems with getting the spell checker to work

Categories

(Core :: Spelling checker, defect)

x86
All
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: chofmann, Unassigned)

Details

Hunspell hasn't been updated on trunk since July. I'm wondering if one of the many editor changes that landed in the b8/b9 cycle may be causing issues. Of course, without STR, this could be near impossible to fix.
also still don't know how we can calibrate the data from input.m.o to understand if its really an increase in reports, or some other factor like more users, or more visibility of the tool in these recent betas. if its editor who would be the person to try and drill down?
(In reply to comment #2) > if its editor who would be the person to try and drill down? I'm the editor guy, but I'm not sure what I can do without having some STRs to investigate things. A lot of changes has landed inside the editor, but we do have automated tests to make sure that basic spell checking continues to work across changes. Adding qawanted in case QA people can help out here.
Keywords: qawanted
The spell checker has been fixed a lot since this bug was filed. I don't see any specific issues listed in the links here I can actually reproduce locally (Firefox 28.0a1).
Status: NEW → RESOLVED
Closed: 12 years ago
Keywords: qawanted
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.