Each update causes problems
It seems with recent updates, things no longer work as it used to. I am currently using 115.3.0, build ID 20230926115257 on Debian Linux.
It used to be that if you selected the view as "Unread", it would stick with that folder, now it just does it until you leave the folder.
I normally view messages as text since html can be a security issue. There is a button marked "Show HTML", which no longer works. Now I have to select "View", "Message Body as" and then manually select things back and forth.
I used to be able to have a button for the Filter Function to have filter folder or filter message, not it is only a selection for Filter Functions and then I can select what I want to do. This is going backwards.
Under "Unread Folders", often the count is incorrect and it claims that there is a message which is unread, which is false. If I select "Compact View", and then unselect it, the count gets corrected.
There are also other issues which were caused by updates. There is clearly an issue with regards with a lack of testing to ensure things are not getting broken.
All Replies (4)
If you click the Unread button on the Quick Filter Bar, and also click the pin icon at the left end of the bar, the filter is retained when opening other folders.
To show Original html, use v. 9 of this add-on.
Thanks, resetting the settings through the add-on fixes the html issue, but there are still other issues.
Pinning the unread works, but not as before where it was folder by folder, rather than for everything.
There are numerous reports about the QFB on Bugzilla, so there might be improvements and fixes in each subsequent version of 115.
I also see incorrect unread counts on folders regularly. Right now, I 'm seeing there is 1 unread message in a my To Claim box under Expense under Action. When I open it up and read the message in Expense, the unread indicator on the Action folder still shows 1 unread message. I have to open and close the folder to get it to update the unread message count. (Sounds like the Observer pattern isn't implemented quite correctly.)