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
{{ message }}
This repository has been archived by the owner on Jun 25, 2019. It is now read-only.
The PointerEvent spec will soon say that click should be a PointerEvent (in addition to being a MouseEvent). Should auxclick be defined from the start to be a PointerEvent?
My feeling here is that it probably shouldn't require it. Maybe for now just say that it's the same type as click? We should aim for this event to mature into the UI Events spec, and not all UI Events implementors will necessarily implement PointerEvents. So eventually this should just added to the list of events to upgrade in the PE spec. But during incubation it probably belongs here in some optional form.
The text was updated successfully, but these errors were encountered:
The PointerEvent spec will soon say that
click
should be aPointerEvent
(in addition to being aMouseEvent
). Shouldauxclick
be defined from the start to be aPointerEvent
?My feeling here is that it probably shouldn't require it. Maybe for now just say that it's the same type as
click
? We should aim for this event to mature into the UI Events spec, and not all UI Events implementors will necessarily implement PointerEvents. So eventually this should just added to the list of events to upgrade in the PE spec. But during incubation it probably belongs here in some optional form.The text was updated successfully, but these errors were encountered: