You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported by kent78 on 2015-02-10 10:29
I´m using Firefox (version 35.0.1) on Windows 7 Enterprise.
In the below jsfiddle example, when I navigate to the button (using the tab key) and then hitting the Enter key, three separate events is triggered (keypress, keydown and keyup) and a message is written to the console for each of them:
Comment 1 by jteh on 2015-02-10 10:57
Many elements in the wild on the web don't support key events; some of them aren't even focusable. Therefore, when in browse mode, the enter key is overridden to activate the control using mouse clicks. Using keys alone just isn't an option, as it would break far too many cases in the wild.
Note that if you're in focus mode, keys are passed unencumbered.
Changes:
Added labels: cantfix
State: closed
Reported by kent78 on 2015-02-10 10:29
I´m using Firefox (version 35.0.1) on Windows 7 Enterprise.
In the below jsfiddle example, when I navigate to the button (using the tab key) and then hitting the Enter key, three separate events is triggered (keypress, keydown and keyup) and a message is written to the console for each of them:
https://jsfiddle.net/kent78/apcjh8uc/
But if I have NVDA running there is no key event triggered at all.
The text was updated successfully, but these errors were encountered: