Closed Bug 279548 Opened 20 years ago Closed 20 years ago

Misspelled words not flagged after turning on inline spell checking

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: skydaemon80, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b) Gecko/20050121 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.8b) Gecko/20050121 Firefox/1.0+

After opening a draft email message for editing and then turning on inline spell
checking via the Options menu of the composition window, misspelled words are
not flagged right away. 

This problem does not occur if inline spell checking is enabled through the
Thunderbird Options dialog box (Composition panel).  In this case, misspelled
words are flagged immediately upon opening.

Reproducible: Always

Steps to Reproduce:
1. Turn off inline spell checking in Thunderbird preferences (Composition panel
of the Options dialog box).
2. Compose a new email message.  Enter a sentence or two with a few misspelled
words.  Save it as a draft and then close the compose window.
3. Find the draft message under the "Drafts" subfolder in the left pane of the
main Thunderbird window, and open it.
4. Choose Options | Check Spelling As You Type.
Actual Results:  
The red underlines do not appear in the misspelled words.  The red underline
appears under the misspelled words only when moving the cursor over them or
clicking before or after them.  Also, until they are flagged as misspelled,
right-clicking the misspelled words only displays the normal context menu for
the compose window.

Expected Results:  
Upon enabling inline spell checking through Options | Check Spelling As You
Type, the inline spell checker should start scanning the entire message for
misspelled words, and underlining them accordingly.
OS: other → Windows 98
please post inline spell issues in the mozilla zine thread. this isn't something
that's even been checked in yet. 
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.