Hi,

I have occasionally experienced this anomaly myself when editing in Chrome with CKeditor. There isn't really anything I can do solve problems with the editors, we rely on the developers of CKeditor and TinyMCE to fix problems. They each have their quirks. I think building the equivalent of a word processor in javascript and keeping up with all the changes in browsers and web standards is a very challenging task so I have huge respect for those developers even though the editors are never quite perfect. Especially now with the way Chrome and Firefox are constantly releasing new versions and automatically updating to them, it seems almost impossible for them to keep up with changes in the browser behavior. I've only noticed this problem recently and suspect it is due to changes in Chrome that have happened after the latest release of Ckeditor.

Your options are:

• try TinyMCE and see how that works for you
• if you've upgraded over time chances are there are older versions of the editors still on disk under /ClientScript you could try configuring it to use an older version from Web.config in case this bug only affects the latest version.
• In the next release coming very soon you will be able to edit the main Html Content instance on pages using Windows Live Writer as discussed on this thread.

Hope that helps,

Joe

Shouldn't have to do that though. I just switched this site to TinyMCE because CKeditor is really causing me lots of problems in Chrome now. I conclude that an update to Chrome changed something because I've been using this version of CKeditor (the latest version 3.6.2) for quite a while and this problem just started happening recently for me. Probably little hacks they had to do previously to make it work right in Chrome are not needed anymore and now causing problems. Hopefully there will be a new release of CKditor soon with a fix for this.