Closed Bug 344596 Opened 18 years ago Closed 7 years ago

spelling checker considers word complete when apostrophe typed

Categories

(Core :: Spelling checker, defect)

Product:
Core
Component:
Spelling checker
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: dbaron, Unassigned)

References

Details

The spelling checker does not mark words that are in the middle of being typed as misspelled.  However, this does not work correctly for words with an apostrophe in the middle.

Steps to reproduce:
 1. load this bug report
 2. click in the "Additional Comments" field
 3. type "aren't weren't shouldn't"

Actual results:
 3. After typing each of the three apostrophes, the current word being typed is underlined until the t is typed

Expected results:
 3. No underlining of misspelled words, since only incomplete words are misspelled.

Additional information:
Bug 237344 is very remotely related.
Assignee: brettw → mscott
Oddly, I never noticed this until the Firefox 3 beta, and it does not seem to affect Thunderbird 2, even though this bug was filed in 2006.  I'm seeing it all the time in Firefox 3, though.  I've added a bunch of "words" to my dictionary that aren't actually words because Firefox can no longer recognize contractions as single words.
Bug 422982 and comment 4 sound more severe than this bug as reported in comment 0, and could be a regression.
Adding to confirm that this bug occurs on the windows version as well.  I'm running Firefox 3, RC2.  Words like "can't" "won't" trigger a bad spelling before the apostrophe.  the description above describes the misspelling underline going away after the word is completed, however I have noticed that the underline remains even after completely typing these words and moving on.
Assignee: mscott → nobody
I think too that Bug 422982 is a more severe regression than this issue because there, the wrong underlining is not removed until the paragraph is closed by pressing "Enter".

A workaround is suggested there and maybe someone can test it.
BTW, on Debian and with their modified FF, this issue seems to be absent.
On Firefox 3.6.12 on OSX, I can't reproduce the issue anymore either. Seems to have been fixed along the way somewhere. Dbaron, can you confirm and close this bug?
WFM current nightly build
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.