82957 - Focus remains on attachments-pane after delete of message

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Christos Cheretakis]

This is the scenario:
- two consecutive messages, containing attachments
- right-click in attachments-pane and save attachment of first message
- press Del to remove current message
- next message becomes current
- press down arrow to move message down, but:
- first attachment of this message in attachments-pane gets focus

Checked with 2001052706 on linux

Comment 1

[Keyser Sose]

Confirmed
Platform: PC
OS: Windows 98
Mozilla build: 2001071604

Marking NEW.

Comment 2

[Wayne Mery (:wsmwk)]

also on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050917
SeaMonkey/1.1a

OS > ALL

Comment 3

[Thomas D. (:thomas8)]

This bug depends on bug 315144 - pressing del on focused attachment deletes message instead - and I believe as soon as that bug is fixed, the focus problems of this bug will also be solved, as it will no longer be possible to use <del> from within attachment pane to delete a msg.

If you agree, please someone with the powers add the dependence on bug 315144.

Comment 4

[Wayne Mery (:wsmwk)]

(In reply to comment #3)
> If you agree, please someone with the powers add the dependence on bug 315144.

not the same, nor related, in part because focus behavior in Thunderbird is not the same, unlike 315144 where SM and TB behavior is same.

Focus issue here about message body is far more reaching than just attachments - I don't see focus on message body of next message unless the body of previous message was focused before hitting delete.  For example, click in message body, then use delete icon last or click in thread pane before hitting delete. Focus never returns to message body. So the suggestion that down arrow show work in these cases is not expected behavior.

Bigger conclusion, SM standard is focus after delete stays in the area of last focus - in the case of this bug, it correctly stays in attachment area, if one exists.

Suggest this bug can be closed invalid.

Comment 5

[Serge Gautherie (:sgautherie)]

(In reply to comment #4)
> Suggest this bug can be closed invalid.

My feeling ? Let's wait (and see) on bug 315144 before making a decision.