Re: [w3c/editing] Removal of browser built-in Undo stack functionality from contenteditable (#150)

> In any case, we should plan for the separate undo stack, because this seems to be the main use case and defacto standard as of now.

We're fine with having that as an option but forcing that on all contenteditable content is definitely not okay for us.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/150#issuecomment-250024532

Received on Tuesday, 27 September 2016 23:05:09 UTC