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

I think @tszynalski  is right in the regard that we shouldn't just disable native undo functionality for all sites. For instance, there are many users of old versions of the google closure editor or old CKEditor versions. They don't have their own undo-stack implementation yet. Disabling native undo-redo by default will definitely break huge chunks of the web. 

Instead, it should be possible to disable & intercept events of the native undo stack if needed. 



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