Expression-Search-NG icon indicating copy to clipboard operation
Expression-Search-NG copied to clipboard

When deleting a message, the next message is not selected (deviation from standard behaviour)

Open ArtimIS-git opened this issue 1 year ago • 4 comments

When deleting a message, the "standard" behaviour of Thunderbird is to select the message below. With this behaviour, one can delete several messages in a row by hitting the "Suppr" key several times.

With the latest version of Expression Search NG, this behaviour is modified. When deleting a message, the next message is not selected. No message is selected. Hitting the "down" arrow selects the second message from the top.

This was tested with : Thunderbird 115.9.0 (64 bits) Expression Search NG v 4.0.30

This is the only extension installed on my profile, so it's easy to replicate: Activate the extension Delete a message There is no further selection

De-activate the extension, reboot Thunderbird Delete a message The "traditional" behaviour is shown (after delete, the next message is selected)

ArtimIS-git avatar Apr 12 '24 10:04 ArtimIS-git

still happening in 4.0.34?

I search for "info", focus a message, delete it, TB then focusses the next message (on Win 11)

opto avatar May 07 '24 19:05 opto

I can confirm this behaviour still exists in 4.0.34. It is, however, not consistent and not search related. Opening TB, selecting a message and deleting it, would:

  • delete the message from the list, leaving no message selected
  • keep the deleted message visible in the message pane This behaviour was consistent and was corrected after disabling ESNG. It reappeared after enabling it again.

However... I then did a search using ESNG and the behaviour disappeared... Until now, nothing I did (restarting TB, disabling/enabling ESNG, changing folders) brought the faulty behaviour back....

Frank071 avatar May 27 '24 09:05 Frank071

look at the last comment on issue#119. There is an updated version there

avegaweiss avatar May 27 '24 11:05 avegaweiss

It is probably related to #113 - but, as said, for now the problem has disappeared. If and when it resurfaces I will try that latest build and do some additional debugging (it took me a while to figure out it was an add-on that caused this, let alone ESNG).

Frank071 avatar May 27 '24 14:05 Frank071