Closed Bug 223416 Opened 21 years ago Closed 15 years ago

spell checker improperly handles length changes in replaced words

Categories

(MailNews Core :: Composition, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jhouse, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030925
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20030925

Notice how in the reproduce steps, you're effectively adding two letters to the
word before where the problem occurs.  It appears that the scanning the
remaining text begins at 2 letters after the end of "relatity", thus skipping
the space and the letter "n".  I suspect that there is somehow a mixing of
positions in the original/corrected blocks of text...

Reproducible: Always

Steps to Reproduce:
1. compose an e-mail with a body of "relatity newsgroup"
2. start the spell check through your favorite method
3. replace "relatity" with "relativity"

Actual Results:  
the "ewsgroup" portion of "newsgroup" gets highlighted and suggests changing it
to "newsgroup"

Expected Results:  
it should not have found any other spelling errors
wild guess: fallout from the JS regexp rewrite?
if this isn't addressed by late monday i'll look at it tuesday. note that
there's a thing about null captures which was changed by the regexp landing
(correctness).
afaik, the spellchecker doesn't use js to replace words, but textservices.
http://lxr.mozilla.org/seamonkey/source/editor/txtsvc/src/nsTextServicesDocument.cpp#2256
QA Contact: esther → core.spelling-checker
*** Bug 229931 has been marked as a duplicate of this bug. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: MailNews → Core
sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.
Assignee: sspitzer → nobody
QA Contact: spelling-checker → composition
Product: Core → MailNews Core
WFM Thunderbird 2.0, Firefox 3.0.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.