You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The CLEditor uses contentEditable attribute only for IE, but Gecko/WebKit also support it a long while.
Particularly, there is a problem with designMode in Firefox https://bugzilla.mozilla.org/show_bug.cgi?id=310488
This means that any flash-based video inserted into text is invisible in rich-text mode and this behaivor brings some issues.
My proposal is to use editor.doc.body.contentEditable=true for every browser. This allow us to see flash video in Firefox in rich-text mode. Though, we should do some kind of hack in Firefox during switching back from source mode to rich-text mode:
// Show the iframe
if (sourceMode(editor)) {
delete editor.range;
editor.$area.hide();
editor.$frame.show();
buttonDiv.title = button.title;
// the next two lines are needed to enable rich-text mode after switching back from source mode
editor.doc.body.contentEditable = false;
editor.doc.body.contentEditable = true;
}
The text was updated successfully, but these errors were encountered:
jzabroski
changed the title
designMode vs. contentEditable and Firefox problem
use editor.doc.body.contentEditable=true for every browser
Mar 6, 2019
Hi.
The CLEditor uses contentEditable attribute only for IE, but Gecko/WebKit also support it a long while.
Particularly, there is a problem with designMode in Firefox https://bugzilla.mozilla.org/show_bug.cgi?id=310488
This means that any flash-based video inserted into text is invisible in rich-text mode and this behaivor brings some issues.
My proposal is to use editor.doc.body.contentEditable=true for every browser. This allow us to see flash video in Firefox in rich-text mode. Though, we should do some kind of hack in Firefox during switching back from source mode to rich-text mode:
The text was updated successfully, but these errors were encountered: