When we use the Navigation (a.k.a Current folder) bar to execute certain functions, it can happen that it applies the command to the wrong folder (if that folder isn't also a QuickFolders tab). I saw this behavior today for the first time, so there must be additional circumstances that give it the wrong document context.
I believe this is a regression from Thunderbird 115
It applies to the changed document context used in QuickFolders.Util.getPopupNode( ).
The function is used by and may have affected the following commands:
Mark Folder as Read
Mark Newsgroup Read
Delete folder (luckily this one asks explicitly with feedback giving the folder name)
Empty Trash
Empty Junk
Delete Junk
Folder Properties
Open Folder in Explorer
Get Messages
Repair Folder
Create New Subfolder
Search Messages
This happened on my production profile today, but I cannot reproduce it on my test profile. IN any case I will make an emergency patch that will use the element.ownerDocument instead of the "global" document variable.
When we use the Navigation (a.k.a Current folder) bar to execute certain functions, it can happen that it applies the command to the wrong folder (if that folder isn't also a QuickFolders tab). I saw this behavior today for the first time, so there must be additional circumstances that give it the wrong
documentcontext.I believe this is a regression from Thunderbird 115
It applies to the changed
documentcontext used inQuickFolders.Util.getPopupNode( ).The function is used by and may have affected the following commands:
Mark Folder as Read
Mark Newsgroup Read
Delete folder (luckily this one asks explicitly with feedback giving the folder name)
Empty Trash
Empty Junk
Delete Junk
Folder Properties
Open Folder in Explorer
Get Messages
Repair Folder
Create New Subfolder
Search Messages
This happened on my production profile today, but I cannot reproduce it on my test profile. IN any case I will make an emergency patch that will use the
element.ownerDocumentinstead of the "global"documentvariable.