Closed Bug 30752 Opened 26 years ago Closed 25 years ago

Scrolling through messages using keyboard is slow

Categories

(SeaMonkey :: MailNews: Message Display, defect, P3)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: rzach, Assigned: hyatt)

Details

(Keywords: perf)

Scrolling through messages using the keyboard up and down keys is exceedingly slow. Apparently every single message is opened and displayed, making fast scrolling impossible. There should be some way to check whether another key event happened before downloading/opening/displaying a message and moving to another message accordingly. Linux build 2000.03.06.09
Keywords: perf
Phil found a way to weasel out of owning this bug. Reassigning.
Assignee: phil → selmer
Scott, reassigning to you because it says perf. I wasn't sure if someone else is looking at navigation, so please reassign if I messed up. Marking M17 since I think we'd ship beta2 without this fix, please adjust if you disagree.
Assignee: selmer → putterman
Target Milestone: --- → M17
nominating for beta3 and moving to M18. cc'ing hyatt. David, is this something the tree widget could handle to prevent selection from happening if someone is scrolling through a tree using the keyboard?
Keywords: nsbeta3
Target Milestone: M17 → M18
Hey David, this got fixed with your scrolling performance improvements, right?
reassigning to hyatt. We think this has improved as part of the scrolling bugs that hyatt did. If I'm wrong and this is something that mailnews needs to control, please reassign back.
Assignee: putterman → hyatt
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
This is now speedy. Resolved as fixed.
This is much faster now because we do not seem open and display messages while scrolling. I tried srolling through 500 messages on a Linux Performance System, took about 190 secs. This is expected because we are scrolling through one message at a time. Using build: 2000-08-17-08 M18 on Red Hat Linux 6.1 (Performance System) Verified: Fixed
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.