Daily 2019-02-28 "Close message window/tab on move or delete" ignored
Categories
(Thunderbird :: Message Reader UI, defect)
Tracking
(thunderbird65 unaffected, thunderbird66 affected, thunderbird67 affected)
| Tracking | Status | |
|---|---|---|
| thunderbird65 | --- | unaffected |
| thunderbird66 | --- | affected |
| thunderbird67 | --- | affected |
People
(Reporter: WoofGrrrr, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0
Steps to reproduce:
Make sure "open messages in NEW MESSAGE WINDOW" is selected
Make sure "Close message window/tab on move or delete" is selected
Open a message (a new window is displayed)
Delete the message from the message window
Actual results:
The next message is displayed in the message window
Expected results:
The message window should go away
Comment 1•7 years ago
|
||
I can confirm this using Thunderbird 67.0a1 Build ID: 0190301092936 and 66.0b2 on Windows 10 and Linux Mint 19.1.
Tabs also don't close, but display the next message.
Comment 2•7 years ago
|
||
Caused by bug 1518823. Already filed: bug 1522460. Mark, what's the point of filing another duplicate?
| Reporter | ||
Comment 3•7 years ago
|
||
Excuse me, but I am not a developer of this software, but merely an end user. This is going to happen with people who aren't actively involved with the development and thus have the time to follow things to the level that developers might.
The previous bug report was filed a while ago, after which it was marked as resolved. I didn't check that it was resolved as a duplicate of some other bug. "Convert TreeBoxObject to XULTreeElement" doesn't mean the same thing to me. It appeared to me that it started working correctly after that resolution, and that it was recently broken again. When I tried to look up any previous bug with a text search, I didn't find it.
I am sorry if my effort to help out with testing do not meet your needs.
Comment 4•7 years ago
|
||
Thanks for testing Daily! It can be bumpy. Resolving a bug as a duplicate doesn't mean that the issue is actually fixed. It's only fixed, if the parent bug is fixed.
In this case we have a severe architectural problem in bug 1518823, that's why it hasn't been addressed. Basically, the Mozilla platform removed a function Thunderbird was relying on and we have yet to decide on how to replace that function. It won't be quick.
Both your previous report in bug 1522460 and this bug here can be found in the duplicates list of bug 1518823.
Description
•