InputEvent: Find out where/how should we fire events for undo/redo |
|||
Issue descriptionCurrently we fire 'undo'/'redo' (to be renamed to 'historyUndo'/'historyRedo') to current focus, but it doesn't make a lot sense since the element to be modified won't get 'beforeinput'. We need to figure out a better solution for this, blocked on spec discussion: https://github.com/w3c/input-events/issues/21
,
Mar 15 2017
,
Jan 11 2018
According to the spec discussion we will stick with firing the event to `undoscope` for now. |
|||
►
Sign in to add a comment |
|||
Comment 1 by chongz@chromium.org
, Mar 15 2017