I don’t know about you, but I figure that if the interface changes in a way that will break code using a previous version, you indicate that this is more than a minor revision in the version number, say “2.1.0”, to suggest to a developer that something more than bug fixes and improvements has taken place. Anyways, I digress.
I’ve experienced a large number of issues with how the editor handles HTML, URLs (in inserted images or links) and other strangeness (lots of >p< >/p< being inserted in code, for example.
The result is that this editor, despite it’s early promise, is pretty much useless for anyone wanting to use it to produce reasonable markup for a CMS. Very disappointing. Looks like we’ll have to switch to Markdown or some form of wiki markup for our purposes.
I know that there are lots of problems with getting these kind of editors to work, especially across multiple browsers. I find it amazing that after all this time we still don’t have decent WYSIWYG editors for use on the web.
Perhaps browser developers should stop messing around with gee-whizzery (like canvas and SVG) just long enough to build a functional editor that produces standards-compliant markup – given that this is such a critical part of the “Web 2.0” experience. And while they’re at it, perhaps agreeing to some standard method of creating validating form controls would be nice too (I have seen that moves are afoot in this regard)…