Closed Bug 303515 Opened 20 years ago Closed 20 years ago

Page Up key does not page up in compose window when replying

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
minor

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 302804

People

(Reporter: ChristianCallsen, Assigned: mscott)

Details

(Keywords: regression)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050803 Firefox/1.0+ Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b4) Gecko/20050803 Firefox/1.0+ Then writing a reply (reply with quoted message start reply below quoted message) and the quoted message is "long", the page up key doesn't page up the quoted message in the email, but appears to page down instead. Reproducible: Always Steps to Reproduce: 1. Select long Email from message list 2. Press "Reply" button (having set include quoted message, start reply below) 3. Try pressing Page Up key. Actual Results: The text in the compose window does not page up. Expected Results: It should have paged up. The scrollbar works fine. But the page up key not working is rather annoying.
Buildinfo from TB: version 1.0+ (20050802)
Reproduced with TB 1.0+0803. I'm seeing a bit of a flicker when I press PageUp -- like it attempted to scroll up, then refreshed with the cursor back down at the end. If you move the cursor up with the arrow keys, then PageUp, the cursor position resets to after the quoted text. Ctrl-Home successfully scrolls the window the top, and PageDn will scroll downwards as expected.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
Version: unspecified → Trunk
Related to/duplicate of Core bug 302804?
Yes, definitely sounds like it. You can probably mark this as a duplicate and transfer CC.
OK, duping. *** This bug has been marked as a duplicate of 302804 ***
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
verified dup
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.