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

@tszynalski It seems like your editor has no cleanup mechanism, so if I paste something from an arbitrary website, it gives me content which is partially non-editable, it throws JavaScript errors, etc. . Is that intentional?

This looks like the kind of editors blogging platforms like Joomla used about a decade ago. I think this can work for a professional web developer who knows how to clean up their content. The issue with not cleaning up the CSS is more with less professional users who publish it directly to their website like that and then break the website. In your case that is probably not as much an issue any more given that all the blogging platforms have editors that clean up content, so the way users get the content out from your editor is to copy and then paste in the other editor where it is being cleaned up.

Does that sound right to you, @tszynalski ? Is there anything you get from execCommand that you could not get if you were to switch to a JavaScript editing framework instead?

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