XHTML Compliance
RadEditor now provides complete XHTML 1.1 compliance, which
has the following two aspects:
-
XHTML compliant rendering on the page (the markup comprising the interface of
the editor, toolbar, dialogs, and so on, is XHTML 1.1 compliant).
-
XHTML compliant content (the HTML being edited)
Although it is not possible to guarantee XHTML compliant content, RadEditor
provides the following tools, which significantly ease the task of producing
valid content:
-
New XHTML Validator module (see the next example)
-
ConvertToXhtml filter (performs client-side XHTML conversion)
-
Xhtml server-side property (available since RadEditor
v3.0)
-
Modified dialogs and Properties Inspector module to facilitate the removal of
non-XHTML compliant attributes
Due to the fact that the editor relies heavily on the underlying browser
rich-edit module there are a number of issues that can negatively affect XHTML
compliance:
-
Use of "FONT" tags
-
Use of "U" tag (for underline)
-
Non-compliant closing of tags, etc.
While the RadEditor can compensate and automatically
convert many of these non-valid tags, the responsibility for producing valid
XHTML compliant content is partially on the side of the user. Therefore, we
strongly suggest the use of the new integrated XHTML Validator for the timely
discovery and correction of non-compliant content.