Closed
Bug 732997
Opened 12 years ago
Closed 7 months ago
Can't select multiple mails using Windows "sticky keys"
Categories
(Thunderbird :: Disability Access, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: gw, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.56 Safari/535.11 Steps to reproduce: I tried to select multiple mails from mail list view using "sticky keys". Actual results: Nothing. Expected results: Clicked mails should have selected.
Comment 1•12 years ago
|
||
That might be XUL tree bug. Enn?
Comment 2•12 years ago
|
||
Can you provide more detailed steps?
Reporter | ||
Comment 3•12 years ago
|
||
A) Sticky keys are disabled: 1. Click to select one message in message list. 2. Press and hold [shift] key 3. Click another message in message list. Result: All messages between are selected and this is correct behaviour. B) Sticky keys are enabled (to enable sticky keys press [shift] 5 times and choose [yes]. 1. Click to select one message in message list. 2. Press [shift] key (do not hold since you enabled sticky keys) 3. Click another message in message list. Result: Second message is not selected and messages between are not selected neither. The same situation is with [ctrl] key (selecting multiple messages at different positions) and also at folder view (while selecting folders).
Comment 4•12 years ago
|
||
It looks like event.shiftKey is true for the mousedown event but not for the click event. It is also false in nsEventStateManager::CheckForAndDispatchClick. Not sure where it might be getting set or cleared.
Comment 5•12 years ago
|
||
Greg, did this work in version 9?
Reporter | ||
Comment 6•12 years ago
|
||
I don't know, because I had not used sticky keys before I replaced my PC with a laptop a month ago.
Comment 7•12 years ago
|
||
(In reply to Neil Deakin from comment #4) > It looks like event.shiftKey is true for the mousedown event but not for the > click event. It is also false in > nsEventStateManager::CheckForAndDispatchClick. Not sure where it might be > getting set or cleared. Is that a confirmation of this bug?
Comment 8•12 years ago
|
||
Yes, I remember seeing the bug, but don't know why it was happening.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Updated•2 years ago
|
Severity: normal → S3
Comment 10•7 months ago
|
||
Flags: needinfo?(erwinm)
Updated•7 months ago
|
Status: NEW → RESOLVED
Closed: 7 months ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•