Closed
Bug 1490641
Opened 7 years ago
Closed 7 years ago
Disable all Gecko specific UIs by default in release build
Categories
(Core :: DOM: Editor, enhancement, P3)
Core
DOM: Editor
Tracking
()
RESOLVED
FIXED
mozilla64
| Tracking | Status | |
|---|---|---|
| firefox64 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
(Depends on 1 open bug)
Details
(Keywords: dev-doc-complete, site-compat)
Attachments
(1 file)
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.
Updated•7 years ago
|
Keywords: site-compat
Updated•7 years ago
|
Priority: -- → P3
| Assignee | ||
Comment 1•7 years ago
|
||
| Assignee | ||
Comment 2•7 years ago
|
||
| Assignee | ||
Comment 3•7 years ago
|
||
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•7 years ago
|
||
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.
Attachment #9009826 -
Flags: review+
Pushed by masayuki@d-toybox.com:
https://hg.mozilla.org/integration/autoland/rev/aeedb5377576
Disable all Gecko specific UIs by default in release build r=m_kato
Comment 6•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla64
Comment 7•7 years ago
|
||
Posted site compatibility note: https://www.fxsitecompat.com/en-CA/docs/2018/firefox-specific-html-editing-ui-has-been-disabled-by-default/
Updated•6 years ago
|
Keywords: dev-doc-needed
Comment 8•6 years ago
|
||
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)
Keywords: dev-doc-needed → dev-doc-complete
You need to log in
before you can comment on or make changes to this bug.
Description
•