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
We currently specify all the possible device independent events that will be triggered after device specific events. These device specific events are largely already accessible to JS in the form of onclick, onkeydown, etc. events, but not all of them (for example choosing "paste" from the right click menu), and they are available in different formats. Should we
a) define new device specific events for the missing device specific events
b) define new and additional device specific events for all of the events that will cause device independent events
c) add information about an events origin to the device independent events?
All of these have their advantages and disadvantages.
From @johanneswilm on August 3, 2015 13:57
We currently specify all the possible device independent events that will be triggered after device specific events. These device specific events are largely already accessible to JS in the form of onclick, onkeydown, etc. events, but not all of them (for example choosing "paste" from the right click menu), and they are available in different formats. Should we
a) define new device specific events for the missing device specific events
b) define new and additional device specific events for all of the events that will cause device independent events
c) add information about an events origin to the device independent events?
All of these have their advantages and disadvantages.
Copied from original issue: w3c/editing#62
The text was updated successfully, but these errors were encountered: