CKEditor 4.1RC Represents a Huge Leap Forward

Version 4.1RC represents a huge leap forward.  The allowedContent feature is spectacular.  With that feature, the editor now becomes the ideal platform for rich text editing of what are mostly articles, reviews, and professional comments, all of which must have a fairly uniform look-and-feel while yet encouraging and facilitating author creativity, with options like links and images.  I chose to implement allowedContent manually.  This approach obviated the need for many configurations, workarounds, and backend processing.  The ui dialog boxes (specifically link and image) conform to the allowed content.  Only the items allowed are represented as items on the various tabs.  Experiments with the easier approach of using the default implementation of allowedContent showed it to be virtually painless and equally valuable.

I upgraded from 4.0.1, which, at least for me, spawned a lot of workarounds.  I have been able to eliminate a lot of code.  4.1RC seems to have resolved a lot of issues I have seen discussed about editor functionality.  I have found no bugs.

I did find the need for one workaround, which carries over from 3.x and 4.0 in a slightly different way.  In those versions, if one removed the height and width features of the image dialog box, one had nevertheless to create an addRules entry to eliminate the height and width from being tacked on to the image as attributes (not styles) in IE.  Curiously, In 4.1RC that became all browsers.  But (1) explicitly removing those elements in the dialogDefinition event (the only place I had to do that), and (2) keeping the rule to remove the attributes in an instanceReady handler, made the elimination of height and width work, either as attributes or styles.  (I am controlling the look and feel of each content result using an external style sheet, and don't want the users to be able to size images.)

Thank you to the CKEditor development team.