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

Ok, but if I understand the alternative correctly it: 

* Imposes having a global undo stack for all input fields on one page, which is not what webapps currently do, not even those by browser vendors such as Google or Microsoft. 

* Doesn't work with collaborative editors where an arbitrary number of items have to be added or removed from some point in the past. 

* If one imports 1000 undo items from previous doc edits that were stored on the server, it means that the history of all other input fields is unreachable. 

But how about this: If you implement that undomanager, it should allow JS to push one fake undo step and one fake redo step when the focus is on the editor and then to consume those when the focus moves away, right? So it would basically be the same thing with the only difference being that JS needs to add 1-3 extra lines of code for Safari. I think that should work! 



-- 
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-249670232