Closed Bug 311369 Opened 19 years ago Closed 19 years ago

keyboard navigation in message and folder lists extremely slow after compose window opened

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 311223

People

(Reporter: Jamie, Assigned: mscott)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) Build Identifier: Thunderbird version 1.6a1 (20051005) After Thunderbird is started, so long as no compose window is opened, keyboard navigation in the message and folder lists is instant, as one might expect. However, once a compose window has been opened (including replying to a message), regardless of whether or not it is subsequently closed, keyboard navigation with the arrow keys in the message list and folder list is extremely slow, such that it seems to lag the system for a second or two. Note that ctrl+arrow keys for multiple message selection appears to work fine. The only way to fix this is to restart Thunderbird. Reproducible: Always Steps to Reproduce: 1. Start Thunderbird. 2. Open a compose window; for example, press ctrl+n. 3. Either: a) Switch back to the main Thunderbird window; or b) close the compose window. This does not matter. 4. Navigate the folder list and message list with the up and down arrow keys. Actual Results: Response was extremely slow, appearing to lag the system after presses of the arrow keys. Expected Results: There should be no lag; keyboard navigation should be as instantaneous as possible. I am using a screen reader (JAWS) and have also tried Narrator in case it was something specific to JAWS, but both exhibit the problem, though Narrator does not appear to be affected as badly as JAWS. It is therefore difficult to determine whether this is attributable to the accessibility (MSAA) support or whether it applies to navigation for the majority of users as well.
Dupe of bug 311223?
Could be, I guess, although this one is not time dependent. It always occurs after the first compose window has been opened.
I just tested 1.5b2. This bug does not occur in 1.5b2, nor does Bug 280287.
*** This bug has been marked as a duplicate of 311223 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
v.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.