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

B.  Adding a fake item, etc... doesn't work because of the way it integrates with the rest of the browser.

Mutating DOM is not necessary at all.  It was merely a convenience feature we wanted to add at the time.

The bottom line is, the only way we can support something like this would be JS authors pushing and popping an entry into and from the native undo stack we manage.  We can provide an API, etc... to associate and dissociate arbitrary JS data.

The thing is I've stated our requirements.  I'm not going into details of what is and what is not possible with the native API because such is an outside the scope of the standardization process.  I'm simply giving an implementation feedback that what you proposed is not implementable, and I've proposed an alternative, which gives full control of DOM mutations and allows authors to remove/add their own undo entries so I don't know what else I can say.

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