2 Answers, 1 is accepted
0
Accepted
Hello Drew,
Originally the only cross-browser element which supported editing was the IFRAME. Subsequently, when Safari (and then Chrome) introduced rich-text edit, they too provided support for the contentEditable attribute - just like IE. Yet, FireFox and Opera did not. As of version 3 FireFox also supports contentEditable.
As most of the browsers now finally support this attribute we can consider providing an "editable DIV" mode to the RadEditor in the future. At present, however, using an IFRAME as a content area is the only option. But apart from browser support there are additional reasons for using an IFRAME - here are a couple:
1. Very often content is created/edited on a admin part of a site, yet it is to be published on the public part of the site. The iframe, being a separate document, allows for using the public site's CSS for styling the content, providing for true WYSIWYG experience.
2. Pasting content - this can have very unpleasant side effects - e.g. pasting content which has a FORM tag in it will corrupt the whole page submission mechanism (which relies on the __doPostBack function).
3. Loading certain elements such as SCRIPTs in an editable div can also have side effects that can affect the whole page in an unpredictable manner.
Best regards,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
Originally the only cross-browser element which supported editing was the IFRAME. Subsequently, when Safari (and then Chrome) introduced rich-text edit, they too provided support for the contentEditable attribute - just like IE. Yet, FireFox and Opera did not. As of version 3 FireFox also supports contentEditable.
As most of the browsers now finally support this attribute we can consider providing an "editable DIV" mode to the RadEditor in the future. At present, however, using an IFRAME as a content area is the only option. But apart from browser support there are additional reasons for using an IFRAME - here are a couple:
1. Very often content is created/edited on a admin part of a site, yet it is to be published on the public part of the site. The iframe, being a separate document, allows for using the public site's CSS for styling the content, providing for true WYSIWYG experience.
2. Pasting content - this can have very unpleasant side effects - e.g. pasting content which has a FORM tag in it will corrupt the whole page submission mechanism (which relies on the __doPostBack function).
3. Loading certain elements such as SCRIPTs in an editable div can also have side effects that can affect the whole page in an unpredictable manner.
Best regards,
Tervel
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Check out the tips for optimizing your support resource searches.
0
Drew
Top achievements
Rank 1
Rank 1
answered on 26 Jun 2009, 07:27 AM
thank you for your detailed response. unfortunately, due to a recent security audit, our company's application cannot use IFRAMES. it is a shame too because our CEO was very impressed with the look and feel of the RadEditor.