HISTORY
We have previously been utilizing FCKeditor for the past 3 years in our online application with success. Yet, after upgrading to the latest version we have hit some issues with the markup that FCKeditor allowed but CKEditor does not and it appear CKEditor attempts to fix by making it compliant
ISSUE
Existing Invalid markup highlighted below in IE 7/8 is resulting in a broken DISPLAY in CKeditor, when switched to SOURCE mode the code shows the culprit.
IE INPUT << (simplified) coming from a database
Notice the <p><td>content</td></p> nesting
CKEditor SOURCE mode in IE 7/8
CKEditor SOURCE mode in FF 3.6
Notice how in IE the in SOURCE MODE you can see the html has been mangled in trying to remove the <p> tag from the <td></td> element Resulting in the HTML to completely BREAK.
QUESTIONS
1. Is there a way to turn of the “compatibility” mode of the CKEditor via config.js that I am just not seeing in the API docs?
2. If there is not a configuration for setting for this could you perhaps point us in the direction in the source code files that would help us get closer to suppressing any kind of compatibility rewrite of the HTML that is being inserted into the editor. IE specific or otherwise.
a. Note: We can’t expect server side scrubbing of our databases (invalid) html data prior to the handing off to the ckeditor, since this could impact our clients existing rendering.
We have previously been utilizing FCKeditor for the past 3 years in our online application with success. Yet, after upgrading to the latest version we have hit some issues with the markup that FCKeditor allowed but CKEditor does not and it appear CKEditor attempts to fix by making it compliant
ISSUE
Existing Invalid markup highlighted below in IE 7/8 is resulting in a broken DISPLAY in CKeditor, when switched to SOURCE mode the code shows the culprit.
IE INPUT << (simplified) coming from a database
<img /><br /> <table cellspacing="0" cellpadding="0" width="640" border="0"> <tbody> <tr>header</tr> </tbody> </table> <table cellspacing="0" cellpadding="0" width="640" border="0"> <tbody> <tr> <td>column</td> <p> <td>content</td> </p> </tr> </tbody> </table>
Notice the <p><td>content</td></p> nesting
CKEditor SOURCE mode in IE 7/8
<img /><br /> <table border="0" cellpadding="0" cellspacing="0" width="640"> <tbody> <tr> header </tr> </tbody> </table> <p> </p> <td> content</td> <table border="0" cellpadding="0" cellspacing="0" width="640"> <tbody> </tbody> </table>
CKEditor SOURCE mode in FF 3.6
<img /><br /> header <table border="0" cellpadding="0" cellspacing="0" width="640"> <tbody> <tr> </tr> </tbody> </table> <p> </p> <table border="0" cellpadding="0" cellspacing="0" width="640"> <tbody> <tr> <td> column</td> <td> content</td> </tr> </tbody> </table>
Notice how in IE the in SOURCE MODE you can see the html has been mangled in trying to remove the <p> tag from the <td></td> element Resulting in the HTML to completely BREAK.
<p> </p> <td> content</td> <table border="0" cellpadding="0" cellspacing="0" width="640">
QUESTIONS
1. Is there a way to turn of the “compatibility” mode of the CKEditor via config.js that I am just not seeing in the API docs?
2. If there is not a configuration for setting for this could you perhaps point us in the direction in the source code files that would help us get closer to suppressing any kind of compatibility rewrite of the HTML that is being inserted into the editor. IE specific or otherwise.
a. Note: We can’t expect server side scrubbing of our databases (invalid) html data prior to the handing off to the ckeditor, since this could impact our clients existing rendering.