Re: [w3c/editing] Contenteditable re-creating deleted children when it shouldn't (Issue #468)

@masayuki-nakano Fine with me. It just seems that means that if you create a pure contenteditable editor (using execCommand and browser undo-stack), your content will be filled with empty inline nodes that the user cannot easily remove. That seems a bit weird, but if we say that the better choice is always to use a JavaScript-based editor that has its own undo-stack, then sure, why not,

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/468#issuecomment-2476781289
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/editing/issues/468/2476781289@github.com>