Get rid of the legacy editor commands which are not used in the wild
Categories
(Core :: DOM: Core & HTML, enhancement, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox105 | --- | fixed |
People
(Reporter: masayuki, Assigned: masayuki)
References
Details
Attachments
(3 files)
Starting from 92, we disabled them in Nightly channel (bug 1706266). And there is no regression reports, but according to the telemetry result (added in bug 1706268), some commands may still be used.
document.execCommand("contentReadonly")
document.queryCommandSupported("insertBROnReturn")
ordocument.queryCommandEnabled("insertBROnReturn")
I think that we could try to disable them in early beta too. However, I don't think we should delete them immediately because they are used constantly in multiple beta releases.
The other commands are really rare and these counters have been stopped collecting the usage.
So we can delete them.
Assignee | ||
Updated•1 year ago
|
Assignee | ||
Comment 1•1 year ago
|
||
Ah, we should disable them in beta/release channel first.
Assignee | ||
Comment 2•1 year ago
|
||
Oops, they are already disabled in release channel. So, we should delete them. Sorry for the spam.
Assignee | ||
Comment 3•1 year ago
|
||
increaseFontSize
, decreaseFontSize
, gethtml
, heading
and readonly
commands were disabled for a year in all channels, but no regression reports
have been filed. Therefore, we can delete the commands and the telemetry
probes.
Note that cmd_getContents
command which is the internal command of gethtml
is not used in comm-central too. Therefore, this patch deletes the command
handler, nsClipboardGetContentsCommand
, and Command::GetHTML
too.
Assignee | ||
Comment 4•1 year ago
|
||
This is a trial to get reports of breakage of web apps in the wild from beta
users. Currently we don't have any bug reports from Nightly users, but according
to the telemetry in Beta channel, there are some web apps using it (perhaps,
for feature detection or one of finger prints) because we get over 1k pings
per day.
If we won't have any regression reports with this, perhaps, we could try to
roll out to disable these commands.
Depends on D153720
Updated•1 year ago
|
Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/6c8bd45039f6 part 1: Get rid of unused editor commands in the wild r=smaug https://hg.mozilla.org/integration/autoland/rev/99538761dfaf part 2: Disable Gecko specific commands which are disabled only in the Nightly channel in early beta too r=smaug
Comment 6•1 year ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/6c8bd45039f6
https://hg.mozilla.org/mozilla-central/rev/99538761dfaf
Comment 7•1 year ago
|
||
I think you set the pref reversed. It should be enabled when @IS_NOT_EARLY_BETA_OR_EARLIER@
is true.
Assignee | ||
Comment 8•1 year ago
|
||
(In reply to Mathew Hodson from comment #7)
I think you set the pref reversed. It should be enabled when
@IS_NOT_EARLY_BETA_OR_EARLIER@
is true.
Oh, right!
Assignee | ||
Comment 9•1 year ago
|
||
This is my silly mistake. I set reverted value to the prefs and the expectation
of WPTs. We need to enable them in late beta and release and disable them in
early beta and nightly.
Comment 10•1 year ago
|
||
Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/af94f567070c part 3: Revert the pref value to enable legacy editor commands in late beta and release r=smaug
Comment 11•1 year ago
|
||
bugherder |
Assignee | ||
Comment 12•1 year ago
|
||
(In reply to Mathew Hodson from comment #7)
I think you set the pref reversed. It should be enabled when
@IS_NOT_EARLY_BETA_OR_EARLIER@
is true.
I forgot to say, thank you for pointing out it.
Description
•