Spell check not working in subject after "Compose Message To" when at least one non-English dictionary is used
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(thunderbird_esr115 affected)
| Tracking | Status | |
|---|---|---|
| thunderbird_esr115 | --- | affected |
People
(Reporter: betterbird.project+15, Unassigned)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
|
5.50 KB,
image/png
|
Details |
1884761.png
Bug 1790746 improved the spell check situation for multiple dictionaries, but we noticed a case that isn't working, even if only one dictionary is active.
- Use TB Daily in en-US
- Install another dictionary, tested with German
- On a message header, right click on the sender and select "Compose Message To" from the context menu
- In the new compose window without further clicks, start entering the subject, for example "heute" (today).
The word is marked as misspelled and a right-click onto the subject confirms that German is not selected, instead, subject and body are out of sync.
Our fix for bug 1790746 (first reported as bug 1775376) now here didn't show this issue. So re-introducing some elements from this patch into the fix from bug 1790746 solves this issue:
https://github.com/Betterbird/thunderbird-patches/blob/main/115/bugs/NNN11-fix-multiple-dicts.patch
|
Reporter | |
Updated•1 years ago
|
|
||
Updated•1 year ago
|
|
||
Comment 1•1 year ago
|
||
I can't reproduce this bug.
|
|
Reporter | |
Comment 2•1 year ago
|
||
Easily reproducible on Windows. German dictionary installed, "compose message to" via context menu of another message, here is the result. It only fails when "compose message to" is used from the context menu.
|
||
Comment 3•1 year ago
|
||
Hello,
I have tried to reproduce this issue using Windows 11, macOS 14 and Ubuntu 22 with 115.13.0(20240709183211), 128.0esr(20240710185639), 129.0b1(20240708223515) as well as the affected build from 2024-03-11 and did not succeed.
I have tried to request a Need Info from the reporter to see if this issue still occurs with the same repro steps and maybe help us with a regression, but it seems that the account has been disabled.
Alongside with the fact that Magnus also confirmed in comment 1 that he does not reproduce this issue, marking this as WorksForMe.
Description
•