Closed Bug 922648 Opened 11 years ago Closed 10 years ago

Inline spell check clears errors when it shouldn't

Categories

(Thunderbird :: Untriaged, defect)

Product:
Thunderbird
Component:
Untriaged
Version:
24 Branch
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 1100966

People

(Reporter: rvjanc, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:25.0) Gecko/20100101 Firefox/25.0 (Beta/Release) Build ID: 20130926170421 Steps to reproduce: 1 - Compose document with two or more errors in the same sentence. 2 - Right click to correct one of the errors. 3 - Red line(s) under other error(s) disappear even though errors have not been corrected. Actual results: See above Expected results: Red line(s) should not disappear on words not corrected.
Confirmed in Thunderbird 24 Doug Kerr
Confirmed in Thunderbird 24.0.1 Doug Kerr
Confirmed in Thunderbird 24.0.1
I tried the above in tb 24.0.1 and did not observe as described above. I started a new mail message, no subject, and entered this text: Two or more errtors in the samk sentence.[newline] I right-clicked on "samk" and chose "same" from the list of suggestions. The word "errtors" remained underlined with red. I did UNDO to re-break the word and tried again with "errtors" corrected to "errors" and "samk" remained underlined. Note that this bug was originally filed under 25.0-Beta.
I tried the above in tb 24.0.1 and the PROBLEM REMAINS. I started a new mail message, no subject, and entered this text: Two or more errtors in the samk sentence. [NO NEWLINE] I clicked on "samk" and selected same. BOTH ERRORS WERE CLEARED even though errtors was still there. TB24.0.1 on OSX 10.8.5
NEW INFORMATION, using Two or more errtors in the samk sentence. If I click on "samk" and select "same" BOTH ERRORS ARE CLEARED. However, if in a new compose window If I click on "errtors" and select "errors" ONLY THAT ERROR IS CLEARED, THE "samk" ERROR REMAINS. Note that this result ONLY happens when I start each test in a new compose window. If I play around in the same window results are unpredictable.
Hmm... I just tried exactly what you described in comment #5 and only "samk" -> "same", the other error remained. I left "TO" field, subject, everything blank. Just "CMD-N TAB TAB Two errorts in the samk sentence." then right-clicked on "samk", etc. Anything else different we might be doing? My currently-enabled add-ons: AdBlock Plus 2.4 Enigmail 1.5.2 LookOut 1.2.13 Remove Duplicate Messages 0.1.13 Test Pilot for Thunderbird 1.3.9
OK I tried a number of things using Two or more errtors in the samk sentence. I pasted it in using "Paste Without Formatting" or shift + command + "V" on Mac into the compose pane with To: blank Subject: blank Some specifics: OSX10.8.5 Compose font Verdana TB24.0.1 with add-ons TB24.0.1 in safe-mode Early Bird 26a [2013-10-12] with add-ons Early Bird 26a [2013-10-12] in safe-mode If I click on "samk" and select "same" BOTH ERRORS ARE CLEARED. However, if in a new compose window If I click on "errtors" and select "errors" ONLY THAT ERROR IS CLEARED, THE "samk" ERROR REMAINS. I also tried this using Two or more errtors in the samk sentence.[return][return] Two or more errtors in the samk sentence. With the same result. I also tried it by typing in "Two or more errtors in the samk sentence." rather than the "Paste Without Formatting" with the same result. Add-ons when not in safe mode: - Adblock Plus 2.4 - Deselect on Click 1.0.5 - Deselect on Delete 1.0 - DOM Inspector 2.0.14 - Extension List Dumper 1.15.2 - MagicSLR 3.9.1 - Saved Password Editor 2.7.1 - Send Later 4.2.2 - Toggle HTML Toolbar Button 0.6.0.8 - ViewAbout 2.0.1 WORK AROUND!!!!!! 1 - Type some junk in the compose window like "klfjisfl" 2 - Select all, command + "A" on Mac 3 - Hit the delete key 4 - Do the things described above 5 - Problem is GONE!
R, I confirm this. Once having done Select all Delete, the window then seems to be behave properly in any situation I have been able to contrive so far. Nice catch. A very usable workaround. Doug Kerr
In addition to a workaround, it should point the DEV's to the actual code issue. It may not be a high enough priority though. Now my issue is to get my wife to use the workaround and stop bugging me. Good thing she is an excellent speller :)
Further insight: • Open Write window • Enter a line with several spelling errors. • Select the whole line • Do Copy • Correction of errors does not proceed properly. • Select all, do Delete. • Enter a line with several spelling errors. • Correction of errors proceeds properly. • Select all, do Delete. • Do Paste (depositing the originally-entered errored line). • Now correction does not proceed properly. However, examination of the Copied text does not show anything strange in it. Curious. Doug Kerr
I also have this problem. I have tried copying the text Two or more errtors in the samk sentence. into a new email correcting the second error and both errors disappear. I've tried typing the same sentence and correcting with the same result. I can confirm that select all and delete clears the problem. I have noticed that the read wiggly line reappears just after I press the send button, which is really annoying. I am on: Thunderbird 2.3.0 English GB dictionary Windows xp service pack 3 It was a while back when I reported a bug with part words getting marked as spelling errors. That error only occurred when the user had a custom default font set. I've just checked and reseting the default font clears the problem. This is clearly a similar problem to the first one I reported which eventually got fixed and broken again. Kim
Also see bug 1100966. I wonder whether both have the same cause.
Re. comment #9: Even after "Select all, delete" the problem can still be reproduced. Typically the clearing happens when you click to position the cursor to a wrong word, correct it, click at the end of the text and at some stage press "backspace". That's when the red lines are cleared.
Status: UNCONFIRMED → NEW
Ever confirmed: true
I am making this a duplicate of bug 1100966. Bug 1100966 is about the core editor messing up the spell checking when "ranges" (an internal concept of the Document Object Model, DOM) are merged during editing operations. If more spelling problems exist after bug 1100966 is fixed, we will need to open another bug.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.