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

@dmonad @tszynalski The proposal of removing the undo stack altogether for contenteditable has been superseded by the undo manager proposal since [1]. This ticket was just not closed yet as I was waiting for the undo manager proposal to be updated and put in the right place. But maybe I should so we don't need to debate this any more.

Sorry for not mentioning that earlier, but that's the reason I'm more interested in the question of whether or not we have found an actual usecase for execCommand here. It sounds like that's not actually the case, right?

[1] https://github.com/w3c/editing/issues/209

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

Received on Wednesday, 27 November 2019 17:46:17 UTC