Open Bug 131307 Opened 23 years ago Updated 13 years ago

right-click delete/move to context menu commands ensures the original row is visible

Categories

(SeaMonkey :: MailNews: Message Display, defect)

defect
Not set
minor

Tracking

(Not tracked)

People

(Reporter: ssu0262, Unassigned)

Details

steps to reproduce: 1) select a message in the thread pane 2) scroll until the selected message is no longer in view 3) right-click on any message and select either the delete or the move to command notice that the originally selected row is brought back into view after the command is executed. It was recommended that this not be the default behavior. It should not scroll, but stay where it is.
one of the reasons for not performing the autoscroll is in the case of the thread pane containing thousands of messages. Scrolling to the bottom and deleting or moving a message (via the right-click context menu path) will force the user to rescroll back to where they were due to the autoscroll.
Status: NEW → ASSIGNED
Keywords: nsbeta1
QA Contact: esther → laurel
I'd argue that this is not that common of a scenario, and could wait until after 1.0
Discussed at Mail News bug meeting with Engineering, QA Mktng and PjM. Decided to minus this bug.
Keywords: nsbeta1nsbeta1-
Severity: normal → minor
Product: Browser → Seamonkey
Assignee: ssu0262 → mail
Status: ASSIGNED → NEW
QA Contact: laurel
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
This is also one of my minor peeves...
Yeah, this is _very_ annoying.
Status: UNCONFIRMED → NEW
You need to log in before you can comment on or make changes to this bug.