Disable overflow/underflow events in release
Categories
(Core :: Layout: Scrolling and Overflow, task, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox131 | --- | fixed |
People
(Reporter: gregp, Assigned: gregp)
References
(Blocks 2 open bugs)
Details
(Keywords: dev-doc-needed)
Attachments
(1 file)
Specifically, disable these these prefs:
layout.overflow-underflow.content.enabled
layout.overflow-underflow.content.enabled_in_addons
Rob's analysis in bug 1897595 comment 25 shows that usage of these events in addons is negligible, so it should be safe to to toggle both prefs in the same release.
Assignee | ||
Comment 1•7 months ago
|
||
Updated•7 months ago
|
Comment 2•7 months ago
|
||
The patch has been approved but should land in 3 weeks, when Nightly is bumped to 131. This deprecation matches what had been documented before at https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/128#changes_for_add-on_developers
Updated•7 months ago
|
Comment 3•7 months ago
|
||
There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:gregp, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.
Assignee | ||
Updated•7 months ago
|
Comment 6•7 months ago
|
||
bugherder |
Comment 7•7 months ago
|
||
I think the removal of these two events should be documented, even when they are non-standard, so I've added the dev-doc-needed
flag.
Sebastian
Comment 8•6 months ago
|
||
Do we still support these events in chrome / system-privileged docs? Is there a follow-up to unship it there, too? (cf. https://searchfox.org/mozilla-central/rev/b1b87f95ecea00828298d1b3cd3d8718f9fcc3fc/browser/components/tabbrowser/content/tabs.js#1261 - but there are other instances as well)
Assignee | ||
Comment 9•6 months ago
|
||
Do we still support these events in chrome / system-privileged docs?
Is there a follow-up to unship it there, too?
Not at the moment.
Assignee | ||
Comment 10•6 months ago
|
||
Emilio, should removing all usage of these events in chrome contexts be a goal?
Comment 11•6 months ago
|
||
I think it'd be worth it, yes. If only because they're not super-reliable.
Comment 12•6 months ago
|
||
Thanks both, I filed bug 1913278.
Description
•