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

That sounds fascinating. Could you paste a link to that service here?

On Wed, Nov 27, 2019, 07:01 tszynalski <notifications@github.com> wrote:

> @johanneswilm <https://github.com/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 were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/editing/issues/150?email_source=notifications&email_token=AAERMOBIGMNUQXVTHRMS5ETQVYEKPA5CNFSM4CQW2SH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFIMW2Y#issuecomment-558943083>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAERMOHZF3H3PXOVEJWM5NDQVYEKPANCNFSM4CQW2SHQ>
> .
>


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