Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
gked opened this issue Jul 29, 2016 · 3 comments
Closed

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

gked opened this issue Jul 29, 2016 · 3 comments

Comments

@gked
Copy link

gked commented Jul 29, 2016

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?

@gked
Copy link
Author

gked commented Jul 29, 2016

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.

@garykac
Copy link
Member

garykac commented Aug 1, 2016

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
Copy link
Contributor

This issue was moved to w3c/input-events#15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants