Okay, I reproduced it in Thunderbird Daily, but... (In reply to Francesco from comment #14) > Hmm, surely with some effort the STR in comment #9 (from comment #4) can be executed via JS in Firefox using `document.execCommand("fontName", ...` and produce the same failure. [I've not reproduced this in Firefox yet](https://jsfiddle.net/d_toybox/p3dax8gm/). How did you reproduce this in Firefox? > Furthermore, as I understand it, Bugzilla classifies by code module, so a bug in the editor code goes into Core:Editor, even if it's only (easily) reproducible in TB. If you consider the upstream/downstream model, FF being upstream and TB being downstream, this is an upstream bug. The editor code is complicated. Some features are used only in Thunderbird, and chrome script in it also does something special. "Core" is managed by Mozilla directly, but cannot work Thunderbird aggressively. Therefore, simply moving to core component, the bug may be not handled in proper priority for Thunderbird users. > As the STR show, it's not related to pasting, it can be reproduced by typing a single character after <enter> and font change. Yeah, and I was completely confused with different bug.
Bug 1840500 Comment 15 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Okay, I reproduced it in Thunderbird Daily, but... (In reply to Francesco from comment #14) > Hmm, surely with some effort the STR in comment #9 (from comment #4) can be executed via JS in Firefox using `document.execCommand("fontName", ...` and produce the same failure. [I've not reproduced this in Firefox yet](https://jsfiddle.net/d_toybox/p3dax8gm/1/). How did you reproduce this in Firefox? > Furthermore, as I understand it, Bugzilla classifies by code module, so a bug in the editor code goes into Core:Editor, even if it's only (easily) reproducible in TB. If you consider the upstream/downstream model, FF being upstream and TB being downstream, this is an upstream bug. The editor code is complicated. Some features are used only in Thunderbird, and chrome script in it also does something special. "Core" is managed by Mozilla directly, but cannot work Thunderbird aggressively. Therefore, simply moving to core component, the bug may be not handled in proper priority for Thunderbird users. > As the STR show, it's not related to pasting, it can be reproduced by typing a single character after <enter> and font change. Yeah, and I was completely confused with different bug.
Okay, I reproduced it in Thunderbird Daily, but... (In reply to Francesco from comment #14) > Hmm, surely with some effort the STR in comment #9 (from comment #4) can be executed via JS in Firefox using `document.execCommand("fontName", ...` and produce the same failure. [I've not reproduced this in Firefox yet](https://jsfiddle.net/d_toybox/p3dax8gm/2/). How did you reproduce this in Firefox? > Furthermore, as I understand it, Bugzilla classifies by code module, so a bug in the editor code goes into Core:Editor, even if it's only (easily) reproducible in TB. If you consider the upstream/downstream model, FF being upstream and TB being downstream, this is an upstream bug. The editor code is complicated. Some features are used only in Thunderbird, and chrome script in it also does something special. "Core" is managed by Mozilla directly, but cannot work Thunderbird aggressively. Therefore, simply moving to core component, the bug may be not handled in proper priority for Thunderbird users. > As the STR show, it's not related to pasting, it can be reproduced by typing a single character after <enter> and font change. Yeah, and I was completely confused with different bug.