July 29th F2F Agenda Item - History handling (undo/redo)

[johanneswilm]

From @gked on July 29, 2016 20:16

What should the relationship between browser-controlled editing history and beforeInput event be? Should redo/undo have beforeInput events? If JS handles beforeInput events, should the browser try to figure out what changes were made? Is that technically possible?

Copied from original issue: w3c/editing#136

[johanneswilm]

From @gked on July 29, 2016 20:22

Resolution: Should redo/undo have beforeInput events? Yes. What should the relationship between browser-controlled editing history and beforeInput event be? Browser Undo stack stays un-affected and dom is not being affected. If JS handles beforeInput events, should the browser try to figure out what changes were made? Is that technically possible? left for future discussion, not blocking beforeInput event spec.

[johanneswilm]

From @garykac on August 1, 2016 20:49

event order:

• beforeinput type='undo'
• undo/redo event
• Dom update
• input

If preventDefault:

• No DOM update
• no input event fired
• The browser undo/redo stack is not changed

[johanneswilm]

This has mostly been added to the draft, but the event order needs to be added to some spec still.