Closed Bug 87170 Opened 24 years ago Closed 24 years ago

[RFE] Improve scrolling in mail

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 4302

People

(Reporter: fleona, Assigned: sspitzer)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.1+) Gecko/20010620 BuildID: 2001062015 If you are reading email and you put the cursor on the last line, then when you scroll up with the keyboard, you need to use the mouse to click on the line you want to type in, because scrolling with the keyboard (or mouse) does not move the cursor, it just moves the screen. When you are typing an email, you are using the keyboard right? Who wants to use the mouse to update the cursor if it's faster and confy to do it with the keyboard? The problem is that the cursor position does not move with scrolling, so this is a request to modify what scrolling does Reproducible: Always Steps to Reproduce: 1.Read or type a long mail (more than the actual screen) 2.Now use page up to go to the top of email. Suppose you wanna write something there Actual Results: Since the cursor is not updated when scrolling, typing gets done in the wrong place Expected Results: Cursor should move with the scrolling, in order to improve user friendlyness and continue the improvement in keyboard use in mozilla
This is pretty annoying on Windows as well. You have to move up one line at a time, because page-up and page-down don't move the cursor.
I would propose a target milestone of 1.0 I hope developers agree that this is very annoying. This is catfood to me
Keywords: nsCatFood
Marking all platforms/os then
OS: Linux → All
Hardware: PC → All
Marking NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** This bug has been marked as a duplicate of 4302 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
verified dup.
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.