My business depends heavily on rich HTML editing (<a href="https:&#x2F;&#x2F;qwilr.com" rel="nofollow">https:&#x2F;&#x2F;qwilr.com</a>) - and I can&#x27;t begin to explain how much time and energy and engineering resource we&#x27;ve poured into trying to improve that experience, and make it reliable across browsers.<p>We had an enormous leg up in that effort - the guy who built the Google Wave editor helped us design and build the core of our editor; even so, its been this massive thorn in our side. Its been months and we still haven&#x27;t gotten our custom editor out into production for all users (just a beta testing subset at this point).<p>I recognise of course the myriad competing forces for engineering time on the browser vendors (&quot;implement X new shiny API!&quot;) - but O how I wish they would agree upon &#x2F; build a rock solid content-editable experience.<p>#totally-selfishly-motivated-whining-complete.