[lioeters]

That's the ideal solution, because (it seems to me that) the issues that break rich text editors are caused by non-interoperable ad-hoc hacks from mobile browsers and operating systems. These rich text editors can work perfectly fine on desktop browsers, yet have countless buggy behavior on mobile. The editor side is not the main problem, it's the mobile side that needs to be fixed and better implemented in a consistent manner across platforms.

[josephg]

I disagree. Rich text editors on the web are already a massive hack, because there aren’t any built in input elements which support rich text. There’s just contentEditable and textarea (plain text). There’s no such thing as “doing it properly” when it comes to rich text. Editors have to hack around what the browser provides via a million event handlers. And - surprise! Mobile browsers don’t expose the same events as desktop browsers.

The right fix is for browsers to have a real rich text element of some sort. Then editors wouldn’t need all their hacks. And mobile browsers would be able to behave correctly when you tap on some editable rich text.