1816412 - Spelling check not correct when using templates

Status: RESOLVED DUPLICATE of bug 1790746

(Thunderbird :: Mail Window Front End, defect)

Description

[Alex]

Attachment: langde.png

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36

Steps to reproduce:

1. Start writing a new mail in a different language than English.
2. Select the corresponding spelling from the Spelling menu selection according to the language you are using.
3. Save this e-mail as a template.
4. Double click the template to start writing a new mail based on that template.

Actual results:

Despite the correct language will be selected in the Spelling menu, all words will be marked with red wavy underlines indicating spelling errors because the window will perform a spelling check for English language.

Expected results:

The correct language should be applied and the entire contents of the e-mail should not be marked will red underlines as spelling errors.

Comment 1

[Alfred Peters [:infofrommozilla]]

I can confirm the error in the newly opened Composer.
However, the spelling correction is updated here as soon as the body receives the focus.
Alex, is that the same for you?

Comment 2

[PS]

Duplicate of bug 1775376.

Comment 3

[Alfred Peters [:infofrommozilla]]

(In reply to PS from comment #2)

Duplicate of bug 1775376.

No. Bug 1775376 it is about the fact that the Content-Language: header is set incorrectly when saving.
This bug is about loading the languages from the header. This is done correctly here as specified in the header. Only the display is incorrect directly after loading.

Comment 4

[Alex]

(In reply to Alfred Peters from comment #1)

Alex, is that the same for you?

Yes. The extra click into the body removes the problem.

Comment 5

[Alex]

Now, in the latest version (102.10), this got even worse. Opening a message based on template or draft just marks the entire mail content (written in other than EN language) red and a click into the body does not seem to remove the problem any more. Even changing the spelling back and forth does not help to get rid of this.