Since upgrade to version 115, sometimes message list does not update when an email is deleted
Hello,
When I press on the trashcan on a message on the message list, sometimes (but quite often, about one out of 3 times) the message is still displayed on the message list. If I click again on the message title, the row is updated with the message below the deleted one. But the rest of the list is not updated, and the message which was below the deleted one, now appears two times. And then if I select the row below, this is updated with the row below this one, but then this message is displayed two times. And so on, every time I click on the message below.
To illustrate the problem, suppose I have the following message list:
Message 1 Message 2 Message 3 Message 4
When I delete the Message 1, the list does not change. If I click again on Message 1, the list changes to:
Message 2 Message 2 Message 3 Message 4
If I click on Message 2 on the 2nd row, the list becomes:
Message 2 Message 3 Message 3 Message 4
Now when I click on Message 3 on the 3rd row, the list becomes:
Message 2 Message 3 Message 4 Message 4
And so on
The message list corrects itself, on two occasions : 1. If I delete the 1st instance of a doubly displayed message 2. If the doubly displayed message is a thread and I expand that thread by clicking on the 1st instance of that thread
所有回复 (5)
Does it work with Help > Troubleshoot Mode?
Yes, It seems it works in Troubleshoot Mode. At least the problem did not appear during about 20 deletions.
But I do not have any extensions installed, on any of the 3 pc's I use, and the problem appears on all. On my laptop it is a fresh installation, done 2 months ago.
The other difference in the Troubleshoot mode is the view, it is a 2 line view. My normal view is an one line message list, with the delete icon column on every message. That's the one I press to delete messages.
Thank you for your help
I noticed that by deleting each e-mail with the keyboard DELETE key (after selecting it first), the problem does not occur.
Please post your results with 115.5.2 which ships next week.
The problem still occurs in 15.5.2