-
Notifications
You must be signed in to change notification settings - Fork 24
should TouchEvent define getModifierState #41
Comments
They're definitely valuable in touch laptop scenarios (eg. I know some users do ctrl-tap to open links in new tabs, just like ctrl-click). I don't see any reason why TouchEvent should be different from MouseEvent / PointerEvent with respect to modifiers. Certainly hard to argue this is very important though. |
In blink the implementation is there; the IDL just needs to be modified so the bindings code will call the implementation. |
still relevant to extend the IDL at this stage, or are we happy to leave as is and focus on pointer events instead? |
Meh, seems pretty low priority to me, but also very low cost to just fix to do the right thing consistent with MouseEvent/PointerEvent. If someone (eg. @dtapuska or someone on his team) wants to take a few minutes to submit a PR and expose this in some implementation, then I'd be happy to see it added to the spec. Otherwise this could be closed as too low priority. |
@patrickhlauke patrickhlauke how is this #91 |
It seems odd to define the alt, meta, ctrl, shift keys on Touch Events; but nonetheless they are there.
We should define the getModifierState defined in https://w3c.github.io/uievents/#widl-KeyboardEvent-getModifierState if we do #40
The text was updated successfully, but these errors were encountered: