Intent to unship: Gecko specific edit commands for `Document.execCommand` and related methods

98 views

Skip to first unread message

Masayuki Nakano

unread,

Nov 8, 2021, 6:20:11 AM11/8/21

to dev-pl...@mozilla.org, Makoto Kato, smaug, Anne van Kesteren

Summary: We still support some Gecko specific edit commands for `Document.execCommand`, `Document.queryCommandEnabled`, `Document.queryCommandSupported`, `Document.queryCommandState` and `Document.queryCommandValue`. The list is here:

`increatefontsize`
`decreasefontsize`
`gethtml`
`contentReadOnly`
`readonly`
`insertBrOnReturn`

Except `contentReadOnly` and `insertBrOnReturn`, those commands are used almost 0 web apps according to the telemetry results so that it must be safe to unship them immediately. So I'd like to unship them right now.

On the other hand, `contentReadOnly` and `insertBrOnReturn` are used less than 1%, but the actual number of documents which run and/or refer them is about 10k. However, those command result is not trivial so that it does not make sense to use these commands in web apps which support all browsers. Therefore, I guess that they are run in automated tests somebody else or technical demo. But for making it safer, I'd like to unship these two commands only in Nightly channel for now.

Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1706266

Standard: N/A

Platform coverage: all

Preference: dom.document.edit_command.*.enabled

DevTools bug: N/A

Other browsers: Nobody has implemented these commands except us

web-platform-tests: Contained in the patch

Security and Privacy: Nothing which we need to worry about

-- 
Masayuki Nakano <masa...@d-toybox.com>
Working on DOM, Events, editor and IME handling for Gecko

Reply all

Reply to author

Forward

0 new messages