User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; GTB6; .NET CLR 1.1.4322; .NET CLR 2.0.50727) Build Identifier: version 184.108.40.206 (20090605) My spell check is set to automatically run when I Send a message. It does this fine. But after it checks the content of the message, it displays errors that do not exist. The same errors appear every time: fareast MsoPlainText (3 times in a row) fareast (again) SpellE spl There were originally a few more errors, but I added them to the dictionary in an attempt to fix it. This started a few builds back, not the most recent one. Reproducible: Always Steps to Reproduce: set up: Options, Composition, Spelling: both boxes are checked (Check spelling before sending and Enable spell check as you type) Language: English US 1. write a message, or send a blank message 2. Press SEND 3. correct all spelling errors in the actual message Actual Results: After my actual message is checked, errors are displayed for words that are not in my document. Even if there are no errors in my message, these non-existent words are displayed. The same errors appear every time: fareast MsoPlainText (3 times in a row) fareast (again) SpellE spl Expected Results: It should send the message after completing the spell check of document. It should not display errors that don't exist. This started a few builds back, not the most recent one. I think it was the first 2.x build. I thought it might get fixed in the next build, but hasn't, and there have been a few updates since. My workaround is to click on Send in the Spell Check box once it reaches the first nonexistent error.
Reporter can you attach an email example for this behaviour?
(In reply to comment #1) > Reporter can you attach an email example for this behaviour? to do that save the email showing the trouble in .eml using File -> Save and come back to this bug and press the add an attach... link.
Created attachment 389944 [details] test message Here is a test email that generated the errors described in the bug.
Confirmed here on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:220.127.116.11pre) Gecko/20090830 Lightning/1.0pre Shredder/3.0b4pre ID:20090830110948 using attached testcase. STR: 1. set option "check spelling before sending" ON and "enable spell check as you type" OFF; 2. open testcase with File-->Open-->Saved message; 3. in open message go to Message-->Edit message as new 4. send message; 5. TB check form word that not are in message (but are in message source) At this moment I can't find any dupe.
can you reproduce in v3.1 or trunk builds? note also I suspect "compose in html" might be required in account settings. WFM Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.3a6pre) Gecko/20100621 Shredder/3.2a1pre
Yes, I am still having the problem in v3.1. "Compose in html" is activated and always has been. I am now working on a new computer with the latest build and still have the problem.
It seems this bug is similar to bug 591365, which probably came to the party later. One of my clients brought a similar issue to my attention, or rather possibly narrowed the focus a little. They noticed when they forwarded emails their spell check would present additional works not in the message. Researching this further, it only occurs when forwarding HTML messages, particularly those where the font has been explicitly defined in the content of the message. I've noticed it in newsletter type mailings and those where Outlook was used to compose HTML messages. Some of the phrases that the spell checker traps includes: - px, PX (pixel measurements in table formatting?) - Lucida ----- - Grande +-- fonts for formatting - Arial + - Helvetica -+ - color (formatting the text colour in the original message) I'm sure others will occur, however, these are the HTML tags, and values, I've noticed. Plain HTML messages being forwarded didn't cause the spell checker to stumble, nor did creating new, clean, HTML messages. That's just my experience. My problem is with messages that I would like to forward that use extended HTML formatting. The problem manifests itself in the latest stable Tb on both XP and OS 10.6. I don't have Windows 7, so can't test that.