We put off to change this until we get enough telemetry data.
Now, we have a lot of data in Beta 62 users. That indicates that each
specific UI is rarely shown (< 0.5% of all HTMLEditor instances).
However, according to operation count per HTMLEditor instance, some of
them may be used by only a few users intentionally.
Currently, I plain:
- 63 disables the UIs by default only on Nightly and Early Beta.
- 64 disables the UIs by default on all channels.
Then, we'll provide new prefs to enable them by default forcibly. This
allows us to collect telemetry data from testers even before web apps
enable the UIs with execCommand explicitly.
If we'll get new telemetry data of 62 Release and it indicates we
shouldn't change our behavior, we should cancel the changes before
shipping the 64 release.
See the detail of current telemetry result here:
https://bugzilla.mozilla.org/show_bug.cgi?id=1452538#c19
On 2018/04/05 15:58, Masayuki Nakano wrote:
This incompatibility is pointed by W3C's Editing API WG:
https://github.com/w3c/editing/issues/171
Gecko has some specific editing UI of HTML editor.
1. Resiziers of <img>, <table>, absolute positioned elements.
2. Adding new table row/column from buttons.
3. Removing existing table row/column from buttons.
4. Grabber to move absolute positioned element.
Currently, all of those UIs are not implemented by the other browsers.
However, they are available in Gecko by default.
Therefore, web app developers need to disable those features with:
document.execCommand("enableObjectResizing",
false, false); // #1
document.execCommand("enableInlineTableEditing",
false, false); // #2 and #3
So, if web apps don't call them, only Firefox users can modify <img> or
<table> elements as unexpected for their developers.
Additionally, web apps cannot disable only #4.
So, for solving this incompatibility issue, we should:
* Disable those UI by default
* But allow to enable those UI for backward compatibility
* Add new command "enableAbsolutePositionEditing" command for allowing
to enable #4
I'm working on this incompatibility issue in:
https://bugzilla.mozilla.org/show_bug.cgi?id=1449564
--
Masayuki Nakano <masay...@d-toybox.com>
Software Engineer, Mozilla
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
