User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20040913 Firefox/0.10.1 The mouse shortcut to open links in a new window (Shift + LeftClick) doesn't work when I have enabled the Accessibility feature (Use Sticky Keys) in Windows XP. Though I haven't tested, the other mouse shortcuts which involve pressing one of shift, control etc might also be broken. Reproducible: Always Steps to Reproduce: 1. Open "Accessibility Options" in Windows Control Panel. Select "Use Sticky keys." Select "Settings". Uncheck all the options except "Use shortcut". 2. Open Firefox. Shift+Leftclick on a link. 3. Actual Results: Link opens up in the same window. Expected Results: Link should open up in a new window. When "Use sticky keys" is turned off, the links opens correctly in a new window.
Isn't this by definition what sticky keys does? With sticky keys, are you not able to press shift once, let it go, then click the link to open in a new window?
Your suggestion, i.e., press Shift, Release Shift, Leftclick doesn't work. Not that it matters, but what I am trying to acheive works in IE.
Confirmed with both Firefox and Seamonkey: with StickyKeys on, if you tab to a link, press and release Shift, then press Enter, you get the Shift+Enter action, but if you press and release Shift, then left-click, you get the unmodified left-click action. --> Browser on the assumption that it's something shared in the backend about getting key status on mouse events.
Assignee: firefox → aaronleventhal
Status: UNCONFIRMED → NEW
Component: General → Keyboard: Navigation
Ever confirmed: true
Product: Firefox → Browser
QA Contact: firefox.general
Version: unspecified → Trunk
This also applies in Windows 2000 Professional.
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 2 days ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.