1490641 - Disable all Gecko specific UIs by default in release build

Status: RESOLVED FIXED

(Core :: DOM: Editor, enhancement, P3)

Description

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(sick)]

Currently, we have some Gecko specific editing UI:
- Resizers to resize <img>s, <table>s, absolutely positioned elements.
- Inline-table-editing UI to add/remove rows/columns.
- Grabber to move absolutely positioned element.

They are now disabled by default in Nightly and early-Beta. Starting from 64, I'd like to disable them by default even on release channel.

Note that the other browsers do not have those UIs and web apps can enable them with document.execCommand() anyway. Those UI usage is enough low according to the telemetry, but a few users use them aggressively (see bug 1452538 comment 19).

This is a request from W3C Editing API WG.

Comment 1

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(sick)]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=fbc842903ccf21fd9e556409d67920732aa400d3

Comment 2

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(sick)]

https://treeherder.mozilla.org/#/jobs?repo=try&revision=209c0102a48b6beed331ac529fb20be7054fb3df

Comment 3

[Masayuki Nakano [:masayuki] (he/him)(JST, +0900)(sick)]

Attachment: Bug 1490641 - Disable all Gecko specific UIs by default in release build

Currently, we have some Gecko specific editing UI:
- Resizers to resize <img>s, <table>s, absolutely positioned elements.
- Inline-table-editing UI to add/remove rows/columns.
- Grabber to move absolutely positioned element.

They are now disabled by default in Nightly and early-Beta. Starting from 64,
this patch makes them disabled by default even on release channel.

Note that the other browsers do not have those UIs and web apps can enable
them with document.execCommand() on Gecko anyway. Those UI usage is enough
low according to the telemetry, but a few users use them aggressively (see
bug 1452538 comment 19).

This is a request from W3C Editing API WG:
https://github.com/w3c/editing/issues/171

Comment 4

[Makoto Kato [:m_kato]]

Comment on attachment 9009826 [details]
Bug 1490641 - Disable all Gecko specific UIs by default in release build

Makoto Kato [:m_kato] has approved the revision.

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/aeedb5377576
Disable all Gecko specific UIs by default in release build r=m_kato

Comment 6

[Narcis Beleuzu [:NarcisB]]

https://hg.mozilla.org/mozilla-central/rev/aeedb5377576

Comment 7

[Kohei Yoshino]

Posted site compatibility note: https://www.fxsitecompat.com/en-CA/docs/2018/firefox-specific-html-editing-ui-has-been-disabled-by-default/

Comment 8

[Chris Mills [:cmills]]

I have documented this by:

• Updating the descriptions on the execCommand page to say they are disabled by default in Firefox 64 (https://developer.mozilla.org/en-US/docs/Web/API/Document/execCommand)
• Removing mention of it from the experimental features page, as it is no longer experimental (https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Experimental_features)
• Adding a note to the Fx 64 rel notes (https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/64#APIs)