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

> Could Safari take care of inserting this token item into the undo stack when there is focus on the contenteditable element and undo/redo is to be enabled, and then somehow also empty the entire undo/redo stack when it has to be disabled?

Not really. Clearing undo stack is possible but then we'd have no way of inserting undo items back. I investigated this problem four years ago. Please go ahead and read old discussions on public-webapps.

Web apps really need to be using browser's undo stack.  Also, talking about enabling / disabling menu item is extremely shortsighted approach.  There is a reason some operating system provide a high-level abstraction for undo/redo, and any approach that relies on some existent UI tends to be not forward compatible.  For example, how is an assistant technology supposed to expose undo/redo stacks if the only thing the browser knows is that there is something undoable?  We need to be able to describe to the user what undo does.

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