Closed
Bug 232343
Opened 21 years ago
Closed 21 years ago
spell checker broken
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
Thunderbird0.5
People
(Reporter: mscott, Assigned: mscott)
References
Details
Attachments
(1 file)
1.99 KB,
patch
|
mscott
:
review+
bryner
:
superreview+
|
Details | Diff | Splinter Review |
hangs in an infinite loop spell checking the first misspelled word I don't think the recent string useage changes in this file would cause this...
Assignee | ||
Updated•21 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → Thunderbird0.5
Assignee | ||
Comment 1•21 years ago
|
||
I think bug 230840 caused this. more info coming soon
Assignee | ||
Comment 2•21 years ago
|
||
cc'ing Johnny, this loop in the spell checker happened in the builds the morning after the landing for nsIContentIterator which is used by nsTextServicesDocument to iterate over the document for the spell checker. AFter that landing we are no longer iterating to the next word in the document. Looks like the iterator stays on the same word.
Comment 3•21 years ago
|
||
Investigating.
Comment 4•21 years ago
|
||
Hmm, I'm unable to reproduce this hang, using Mail Compose (both plain text and HTML) in SeaMonkey. Got a stacktrace, or more detailed instructions?
Assignee | ||
Comment 5•21 years ago
|
||
the key is to have at least one misspelled message in the compose window and then you have to send the message. This also implies that you have spell check on send set to true.
Comment 6•21 years ago
|
||
I could reproduce with seamonkey when spellchecking a few lines. jsut one or two words didn't work, i needed more. I added a few newlines too. Make sure you have at least a few wrong words. Ignore the misspellings. Now, spellchecks just loops and loops. It will start at the beginning after a few words.
Comment 7•21 years ago
|
||
Ok, I'm seeing it now. Working on a fix.
Comment 8•21 years ago
|
||
Comment 9•21 years ago
|
||
Comment on attachment 140015 [details] [diff] [review] Fix nsTextServicesDocument::GetFirstTextNodeInPrevBlock(). The patch in bug 230840 incorrectly made nsTextServicesDocument::GetFirstTextNodeInPrevBlock() position the iterator at the first text node in the previous block, when all it should do was return the node.
Attachment #140015 -
Flags: superreview?(bryner)
Attachment #140015 -
Flags: review?(mscott)
Assignee | ||
Comment 10•21 years ago
|
||
Comment on attachment 140015 [details] [diff] [review] Fix nsTextServicesDocument::GetFirstTextNodeInPrevBlock(). thanks johnny
Attachment #140015 -
Flags: review?(mscott) → review+
Updated•21 years ago
|
Attachment #140015 -
Flags: superreview?(bryner) → superreview+
Comment 11•21 years ago
|
||
this is probably related to Bug 232173
Comment 12•21 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 21 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 13•21 years ago
|
||
*** Bug 232173 has been marked as a duplicate of this bug. ***
Comment 14•21 years ago
|
||
Confirmed fixed in 2004012808 win32 build. Thanks guys.
Comment 15•21 years ago
|
||
*** Bug 232724 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•