(10/16 Updated with overnight fixes) (10/15 Updated with new dropped-spaces/wrapping bug) (10/9 Updated with overnight fixes, and two new bug bullets) (10/8 Updated subsequent to Rachel's very nice response, with discovery of another bug.) I originally posted the following as a comment in Eric's announcement about the new editor, but it seems more likely to assist staff as a separate bug report. I've tweaked the text a bit from my original comment. It would be helpful to know (by response) whether these issues are being (or cannot be) addressed, either by Instructables staff or by the CKE developers. It seems there are some fairly substantive bugs or obstructive "features" in the newly rolled-out editor. The ones I've collected so far (from reading posts as well as personal experience) are (now grouped separately as "true bugs" vs. "feature changes" or "design issues"): Browser Incompatibility There are serious shortcomings with the new editor on non-Firefox browsers Cannot paste comments at all, mishandling of links, etc. Bugs Additional user-entered spaces left as " " entities, rather than collapsed Pop-up box for hyperlinks is empty (no where to enter/paste a URL) FIXED Inexplicable "invalid formatting" errors FIXED Text pasting interference (hijacking of Ctrl/Cmd-V) FIXED Interference of spell-checker with built-in and configurable facilities FIXED Extra whitespace inserted between HTML markup and adjacent characters FIXED Line wrapping has problems: spaced between words get dropped FIXED Spell-checker mistakes and application to hidden format codes FIXED Feature/Design Issues Extremely slow loading and processing FIXED! FIXED! FIXED! Inconsistent recognition of typed-in URLs (maybe three separate bugs?) FIXED Text box loses keyboard focus and requires multiple mouse-clicks to recover Editor box, icons, and posting button cut off by sidebar Limited keyboard-based markup (only bold, italic, and underlining), no entities Blank-line separation is not identified/translated into proper HTML paragraph tags Redundant end-of-line tag ("") at end of user's text. I realize that you all have already gone through the conversion of the existing database of comments and everything else, so backing this out is essentially impossible. However, it might be worthwhile rolling out fixes for these problems as soon as they're available, rather than waiting for a regular update cycle.