243835 - Selecting a message does not cancel previously queued message selection after message delete

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Graham Leggett]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040301
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040301

While an IMAP mail folder is being browsed, pressing the delete button will
cause two things to happen one after the other:

1) The message is marked as deleted
2) The cursor is moved to the next message

On a slow link (congested modem speed), it may take some time for the action 1
to complete and follow on to action 2. It is possible during this waiting period
between the completion of 1 and the start of 2 for the user to click on a
completely different message 3.

When mailnews catches up and completes 1, it then selects the message in action
2, moving the selected message away from the message 3 selected by the user. If
the user was in the process of doing something to message 3 (for example, moving
it to another folder, or deleting it), that action is now applied to message 2
instead.

What should happen is that as soon as the user selects any message, any queued
message selection actions should be removed from the queue. This will ensure
that when message 3 is selected, it will not be unselected for any reason
outside of the control of the user.

The behaviour of moving the selected message one down after deletion should
stay, it just needs to be improved.


Reproducible: Always
Steps to Reproduce:
xxx

Comment 1

[Graham Leggett]

Is there any progress on this bug? This can probably be described as the single
most irritating feature of Mozilla Mailnews.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.