About as trivial as they come, this one. If you use the Undo function to clear the subject of a new message, the title of the window does not display (no subject). Steps to reproduce: 1. Compose a new message. 2. Enter text in the Subject field. 3. Undo the entry of the text (Ctrl-Z, Alt-Bksp, or through context menu). Expected results: Title of window becomes "Compose: (no subject)" Actual results: Title of window becomes "Compose: "
Dup of bug 320006?
Upon DOMi-ing the window, it appears that the title of the window does indeed contain an extra LF at the end, but the textbox claims to have textLength 0.
David, there is no attention to bug 320006 (nor Bug 147625 which is cited there). so, ... Is compose behavior described intentional and if not, is it worthy of changing? When message is saved as draft after step 3, closed, and reopened from drafts then window is "Compose: (no subject)" - so it's clear that the subject is saved correctly after undo and that window initialization sets "(no subject)". But is "(no subject)" a default that must be restored in the process of editing?
It's not intentional, I don't think, but I wouldn't say it's worth changing.
I only reported it because, for example, typing A ^Z gives a different "result" than typing A <Backspace>. Like I said, about as trivial as they come. :) I just figured it'd be either (a) a small fix somewhere, or (b) symptomatic of some underlying problem that needed fixed.
origin probably goes back to bug 60917 comment 15. in which case probably related to or dupe of these other bugs
Still happens in Thunderbird 188.8.131.52, exactly as described.
This isn't as bad as some of the Firefox bugs which are nearly 10 years old, but it's still marked as NEW and that's just ridiculous. I propose a quick-and-easy solution: don't change the window title at all until the subject field loses focus. This is exactly what Outlook does, and personally I prefer it because seeing the window title change while I'm typing is very distracting.
I think that would be entirely reasonable even if there weren't a bug! I don't know if the bug is an indicator of something slightly awry elsewhere though... undo event handling, or textbox text management, or something.
Did this get fixed by the landing of bug 318065?