Closed
Bug 545043
Opened 15 years ago
Closed 15 years ago
Composed message spelling not re-checked after dictionary changed by Preferences or the subject line context menu
Categories
(Thunderbird :: Message Compose Window, defect)
Thunderbird
Message Compose Window
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 315784
People
(Reporter: tuggyne, Unassigned)
Details
+++ This bug was initially created as a clone of Bug #544448 +++
The message compose window does not immediately re-check spelling after the current dictionary is changed from outside the compose pane, using e.g. the Preferences/Options dialog or the message's own subject-line context menu.
STR:
0. Make sure you have at least two dictionaries installed; to install a new dictionary:
a. Open the Preferences/Options dialog by clicking either Tools -> Options or Edit -> Preferences (depending on OS)
b. Select the Composition section and the Spelling subtab
c. Click the Download more dictionaries link and follow the instructions there
1. Type in a word that's spelled correctly in your current language (but not an alternate language) -- I'll assume en-US and es-AR for the sake of example, and type in "correct" with en-US set as current
2. Change to the alternate language
a. Open the Preferences/Options dialog by clicking either Tools -> Options or Edit -> Preferences (depending on OS)
b. Select the Composition section and the Spelling subtab
c. Select your alternate language from the Language drop-down
d. Click OK and return if necessary to the message compose window
Actual:
Nothing.
Expected:
The given word -- "correct" in this case -- to be underlined with red dots or the like.
If you follow a similar procedure, replacing step 2 with the following, it works as expected:
2. Click the drop-down next to the Spelling button in the toolbar, and choose your alternate language from the list
Spelling will be rechecked appropriately if the text in the compose pane changes, e.g. because of typing.
Reporter | ||
Comment 1•15 years ago
|
||
Need to search for dupes more carefully next time….
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•