1160859 - Spell-check needs to be restarted constantly

Status: RESOLVED DUPLICATE of bug 1100966

(Thunderbird :: Message Compose Window, defect)

Description

[Tim Freedom]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:37.0) Gecko/20100101 Firefox/37.0
Build ID: 20150415140819

Steps to reproduce:

I'm in "safe-mode", using the default "English (United States)" dictionary, start a new email (I'm using TB-31.6.0).  Type "hylo theere howw ", all 3 words should be underlined to note that they are misspelled, corrected the last "howw" word, Oops the first word is no longer noted as misspelled (PROBLEM !).


Actual results:

In longer emails, I have to constantly disable and then enable the spell-checker for it to find and highlight misspelled words (via Options->"Spell Check As You Type" setting).  If I leave it as is about 30-40% of my words go un-highlighted - this happens once I correct a word or two in the middle of my email body.  It looks like correcting a word or two somehow makes Thunderbird lose it settings in knowing what was misspelled and what wasn't.


Expected results:

All misspelled words should ALWAYS continue to be highglied as misspelled no matter what the user does unless he/she corrects the word.

Comment 1

[Wayne Mery (:wsmwk)]

I believe  you will fin dthis fixed in version 38, due out in a few weeks.
When it comes out, if you find it is not fixed please reopen the bug. Thanks.

Comment 2

[Tim Freedom]

Hi Wayne, bug 1100966 notes that the problem was getting triggered due to backspace and needing to reproduce (and replicate) various structures that were otherwise getting lost due to that deletion.  In this bug, there is no backspace (or deletion) utilized and its SUPER simple to reproduce -- can you possibly check with the latest code to see if version 38 does indeed fix this ?

Thanks !!

Comment 3

[Wayne Mery (:wsmwk)]

yes, I have. backspace is only one cause - there are others. At least in my experience

Comment 4

[Tim Freedom]

Great, I'll take your "I have" to mean that you've tested version 38 with the test case and its working as expected.  If that's true, then I'm eagerly looking forward to the release of version 38 :-)

Cheers.