[upstream] Adding word to dictionary doesn't update subject
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mozilla Thunderbird |
Confirmed
|
Unknown
|
|||
thunderbird (Ubuntu) |
Confirmed
|
Low
|
Unassigned |
Bug Description
When composing a new email, if you type a word that's not in the dictionary into the email subject, then type the same word in the email body, then right click on the word in the email body and select "Add to dictionary", the wavy red warning line disappears from the word in the email body, but not from the same word in the email subject.
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: thunderbird 1:78.7.
ProcVersionSign
Uname: Linux 5.8.0-43-generic x86_64
AddonCompatChec
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/pcmC0D0p: alistair 1735 F...m pulseaudio
BuildID: 20210203182138
CasperMD5CheckR
Channel: Unavailable
CurrentDesktop: Unity:Unity7:ubuntu
Date: Tue Feb 23 10:37:30 2021
ForcedLayersAccel: False
IfupdownConfig:
# interfaces(5) file used by ifup(8) and ifdown(8)
# Include files from /etc/network/
source-directory /etc/network/
IncompatibleExt
Lightning - {e2fda1a4-
English (GB) Language Pack - <email address hidden>
Thunderbird (default) - {972ce4c6-
InstallationDate: Installed on 2020-07-14 (223 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
IpRoute:
default via 172.16.0.1 dev wlp0s20f3 proto dhcp metric 600
10.0.0.0/24 dev wg0 proto kernel scope link src 10.0.0.2
169.254.0.0/16 dev wg0 scope link metric 1000
172.16.0.0/16 dev wlp0s20f3 proto kernel scope link src 172.16.69.217 metric 600
PrefErrors: Unexpected character ',' before close parenthesis @ /usr/lib/
PrefSources: prefs.js
Profiles: Profile0 (Default) - LastVersion=
RunningIncompat
SourcePackage: thunderbird
UpgradeStatus: Upgraded to groovy on 2020-10-05 (141 days ago)
dmi.bios.date: 12/07/2020
dmi.bios.release: 1.15
dmi.bios.vendor: LENOVO
dmi.bios.version: N2WET25W (1.15 )
dmi.board.
dmi.board.name: 20U9CTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0R32862 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.ec.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad X1 Carbon Gen 8
dmi.product.name: 20U9CTO1WW
dmi.product.sku: LENOVO_
dmi.product.
dmi.sys.vendor: LENOVO
Changed in thunderbird: | |
importance: | Unknown → Low |
status: | Unknown → Confirmed |
Changed in thunderbird: | |
importance: | Low → Unknown |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14
Build Identifier: version 2.0.0.14 (20080421)
If there is a word in the Subject Line of the email which is flagged as a spelling error (red line underneath) and that word also appears (and is flagged) in the body of the email, adding the word to the dictionary only unflags the word in the location where you added the word to the dictionary, but not in the other location.
Reproducible: Always
Steps to Reproduce:
1. open a new Compose window
2. type "zzv " in the Subject Line (without the quotes, but with a space). Note that the word is now flagged as a spelling error.
3. type "zzv " in the Body of the email (without the quotes, but with a space). Note that the word is now flagged as a spelling error.
4. in the Subject Line, right click on the misspelled word and select "Add to dictionary"
Actual Results:
The misspelled word is no longer flagged in the Subject Line but is still flagged in the body of the email.
Expected Results:
If a word has been added to the dictionary, both the Subject Line and the Body of the email should be scanned to unflag the word.
The error occurs whether you add the word to the dictionary from the subject line or the body of the email. System remains stable.
Note that if you go to add the word to the dictionary a second time the word is accepted. I don't know if this means that there are now two copies of the word in the dictionary, or simply that no error was reported. This is why I am reporting this bug as "Normal" instead of "Minor".