Closed Bug 1854535 Opened 2 years ago Closed 2 years ago

when using addon Mark All Read:WE, focus is lost from side folder panel

Categories

(Thunderbird :: Add-Ons: Extensions API, defect)

Thunderbird 115
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: carl, Unassigned)

References

Details

(Whiteboard: [add-on: Mark All Read:WE])

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0 Waterfox/56.6.2022.11

Steps to reproduce:

  1. install addon Mark All Read:WE from here: https://addons.thunderbird.net/en-US/thunderbird/addon/mark-all-read-we/
  2. add button for addon Mark All Read:WE to the menu bar.
  3. on the left side panel, clicked on folder that has 7 or more unread messages
  4. clicked on mark all button provided by addon Mark All Read:WE to mark all unread messages in that folder as read

Actual results:

All messages in that folder were marked as read and the focus changed from the side panel with the selected folder, to the messages I just had marked as being read.

If I had held down ctrl and clicked on a message so there was no message selected in that folder, selected the folder in the left side panel, and clicked on mark all button, then the same thing would occur where the focus would be lost from the folder in the side panel. Except now nothing would have focus.

Expected results:

Focus should be returned to the selected folder in the side panel.

I don't use the builtin feature with the mark button because I don't want a 2 step process of clicking on its drop down menu where I then click on the option mark all read. I want the button to only have the feature mark all read when I press it.

This feature was working in thunderbird 102 and seems to have regressed since I updated to thunderbird 115.

Sorry we don't track add-on issues in bugzilla. Please contact the add-on author.

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
Whiteboard: [add-on: Mark All Read:WE]

This may be related to Bug 1840072, which I will try to fix soon.

See Also: → 1840072

Thank you!

You need to log in before you can comment on or make changes to this bug.