Modes of Operation
Depending on the element from which the Editor is initiated, it provides two types of operation modes—the classic and the inline mode.
Classic Mode
If you use the default <textarea> element for initializing the Editor, the Editor assumes its classic mode. The textarea is not visible and is used to hold the value of the widget. You can type in the contenteditable iframe that is created.
The classic Editor posts its value automatically because it is based on a form element. The tools of the Editor are always visible. Its content does not reside on the main web page and the styling of the page does not influence the editable content. To apply custom styles to the editable content, inject them through the configuration of the Editor. For a runnable example, refer to the demo on the classic Editor mode.
Inline Mode
If you initialize the Editor from a "div" element, the component assumes its inline mode. The <div> element is content-editable and is used by the component to return its value. For a runnable example, refer to the demo on the inline Editor mode.
While it is possible to initialize an inline Editor from a non-
divelement, such asporh1, it is strongly recommended that you use the<div>one. Do not use<table>elements for creating inline Editors because of Internet Explorer browser limitations.
By default, inline Editors do not post their value and you have to post their value manually. The tools of the Editor are only visible when the component is focused. Its content resides on the main web page and the styling of the page influences the editable content.
Because of the limited
iframesupport by the iOS Safari browser, it is recommended to use the inline Editor mode on iOS devices.