Bug #42: Widget is not keyboard acessible

Title: Widget is not keyboard acessible

Bug

#42

Status

ACCEPTED

Created

2007-10-10 13:40:07

Reporter

Benjamin Joffe

Description

When I press the tab key the focus will pass to the buttons scattered around the UI, but if I press enter they are not triggered. It seems you are detecting "element.onmousedown" instead of "element.onclick", this should be changed to enable people without a mouse, and power users who can use a keyboard faster than a mouse to be able to use the widget effectively.
Also; although the increased responsivity that onmousedown offers may appear as a bonus it is uncomfortable to those who expect a click to be cancellable my mouseing out of the button before onmouseup.

Bug Discussion 1 post

Log in at the top of the page to post a comment.

Ah, looks like this behaviour was fixed in 9.5...
Earlier versions didn't correctly support button elements (as opposed to input[type=button]) - if you 'mousedown'ed then moved the mouse even a tiny amount (which can happen naturally with a click) it would go into 'drag mode' and not send the 'mouseup' event on release, caused all sorts of problems and requiring you to click the button again to release it. This appeared to happen even though I used the '-apple-dashboard-region' fix.

So, the reason for using 'mousedown' instead of 'click' wasn't for response times! I've tested the fix locally, and 'click' seems to be working perfectly, but I probably won't upload this version until 9.5 goes live.

Obviously, this applies to all my widgets that feature buttons, I'll change it globally.

By johnnysaucepn, # Oct 11, 2007 10:17:41 AM