[Webkit-unassigned] [Bug 281430] click events invoked with keyboard have fictitious screenX, screenY, clientX, clientY values

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=281430

--- Comment #2 from Josh Tumath <josh.tumath at outlook.com> ---
(In reply to Alexey Proskuryakov from comment #1)
> Thank you for the report. Could you please clarify why you find it
> beneficial to be able to detect that the event was sent from keyboard? 
> 
> To me, that seems like a downside, as it increases the risk of website
> malfunction for accessibility users - one would want accessibility to take
> normal well-tested code paths as much as possible.

Ironically, I want interoperability on this to help with use cases relating to accessibility.

I work at the BBC and, on our UK website, our navigation bar menu button behaves slightly differently depending on if it is opened with a pointer or keyboard. The click event will always open the menu, but:

- when opening with a pointer, the focus moves to the menu container.
- when opening with a keyboard, there is no animation to open the menu and the focus moves to the first link in the menu.

Often when opening a menu, we don't want a slightly different behaviour around focus and animations depending on if the user 'clicks' with a pointer or keyboard.

The 'click' event is great when creating user experiences for keyboard users because it is device independent. On keyboards, it is only invoked by Space or Enter key presses. If we were to use the keydown event, we would have to check whether only the the Space or Enter keys were pressed.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20241015/08139bd3/attachment.htm>