Open
Bug 769207
(removemutationevents)
Opened 13 years ago
Updated 2 months ago
Get rid of mutation events
Categories
(Core :: DOM: Events, task, P3)
Core
DOM: Events
Tracking
()
NEW
People
(Reporter: ayg, Unassigned)
References
(Depends on 2 open bugs, Blocks 1 open bug)
Details
(Keywords: dev-doc-needed, site-compat)
Mutation events are synchronous, which causes a ludicrous number of bugs and performance issues. We now have mutation observers, and we'd really like to kill support for mutation events at some point in the future. Probably not for a while yet.
In bug 766426 I'm going to have to add some kind of hack to account for mutation events, maybe removing an assert. So I'd like to file a followup to get rid of the hack once we get rid of mutation events, and have it depend on this so we hopefully remember to fix it when we do actually kill mutation events.
Updated•7 years ago
|
Keywords: site-compat
Updated•7 years ago
|
Priority: -- → P3
Updated•7 years ago
|
Keywords: dev-doc-needed
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•5 years ago
|
Type: enhancement → task
Updated•4 years ago
|
Alias: killmutationevents → removemutationevents
Updated•2 years ago
|
Severity: normal → S3
Updated•8 months ago
|
Component: DOM: Core & HTML → DOM: Events
Comment 1•5 months ago
|
||
Per https://github.com/whatwg/dom/issues/305#issuecomment-2302407051 the rollout of removed mutation events is now 99% of Chrome users, though there's an origin trial to keep mutation events supported.
I think we can turn off mutation events in Nightly and also offer an origin trial to keep them supported. When the number of sites in Chrome's origin trial is very low or they remove the origin trial, we should be able to ship to release.
You need to log in
before you can comment on or make changes to this bug.
Description
•