Re: [w3c/editing] When an 'insertHTML' command should be applied as sibling or child of a <font> element ? (#191)

Right. But that doesn't make much of a difference. pre-HTML5 elements should not appear under any circumstances - no matter whether the user hits Enter, or you execute one execCommand or the other. That's why I would formulate a general policy that pre-HTML5 content should be added to contenteditable by the browser under any circumstances. The only thing that makes this case slightly better than it happening upon an Enter-press is that execCommand usage is in itself discouraged and no modern editor uses it any more. 

I also challenge the view that removing the font element breaks existing editors. Using editors on a website generally means that content is being changed and so under almost all circumstances means some kind of setup with server side programming and a database. It's not really possible to have run a page with server side code since before 1997 when HTML 4 was released and not having been hacked since then without updating the site's source code.

So no, I don;t think we should be making changes that again involve a font element. If any browser is being changed, it should be changed so that the font element is gone. 

-- 
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/191#issuecomment-481197527