265306 - user interface suggestion for navigating bottom posted messages

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Message Display, enhancement)

Description

[Eric S. Johansson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040803 Firefox/0.9.3

this is a result of a discussion on the mail-news mailing list.  I wrote:
"""
as irritating as this may be to some folks, after many years of being a rabid
bottom poster I'm starting to see the value of top posting.  its nonintuitive
but I believe it's better human factors given the low usability of current
e-mail clients.  You can see the response right away without doing anything you
can quickly evaluate the message as to whether or not you want to look further,
you can quickly find the latest changes.  What's not to like?  (Yes, I know lots
of things).

My insight on this came from having hands that hurt when you use them. Tapping
on the space bar a half a dozen or more times just to get to the latest
commentary, having no way to go backwards (apparently) other than scrolling with
a mouse is really ugly if your hands don't work right.

(note: by update, I mean the text contributed by the message sender. for example
in this message the first update would start out with "as irritating as")

Having a hotkey or even automatic process to move window focus to the first
update would be a huge improvement.  Being able to jump to the next update would
be wonderful.  Not automatically jumping off of the end of the message to the
next message would be heavenly.  Making all of these capabilities keystroke
bound so that those of us using speech recognition can just dictate commands
would earn significant gratitude.

people use top posting because it fits their cognitive processes better.  Fix
the user interface for bottom posting and people will return to it in preference. 
"""
and was encouraged to file a bug

Reproducible: Always
Steps to Reproduce:
1.
2.
3.

Comment 1

[Robert Kaiser]

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

Comment 2

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420