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

@johanneswilm  For what it's worth, I run a simple, fairly popular web editor for typing foreign characters. It's just contenteditable with execCommand, and currently no programmatic DOM manipulation. I use the native undo stack and it works fine. I wouldn't want to see it gone!

I agree things get ugly quick when you start to combine native editing operations with direct DOM modifications (been there, done that), but currently I have no need for anything beyond Bold/Italic/Underline/Subscript/Superscript.

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