I'm sure that some of you know that our company produces a standards-compliant editor, so I feel uncomfortable about saying this, but there is no way that FCKeditor is standards-compliant. I'm not saying this to get you to buy our product, because our editor is a plug-in and this thread is about in-browser editors. When someone makes claims that a tool is Web standards complaint and it's not, they are actually hurting the Web standards movement. To return to FCKeditor, these are just a few examples of why it's not standards-compliant (tests done in IE):
1. Generates invalid markup: Start with <p>Test</p> and then apply "Custom Bold" from the Styles menu. You get: <span style="FONT-WEIGHT: bold"> <p>Test</p> </span> As you know, an inline element cannot contain a block element. 2. Generates semantically meaningless markup: Start with <p>Test</p> and apply formatting using the color picker and font selector. You get: <p><font face="Verdana" color="#ff0000" size="4">Test</font></p> 3. Generates deprecated markup. For example, create an anchor and you get: <a name="abc"></a> Regards, -Vlad > > -----Original Message----- > From: Michael Kear > > The release candidate for FCKEditor 2.0 claims to be standards compliant... > > Very cool, and easypeasy to use. > > ********************************************************* > The CMS discussion list for http://webstandardsgroup.org/ > ********************************************************* > > ********************************************************* The CMS discussion list for http://webstandardsgroup.org/ *********************************************************
