Please report any other irregularities here.
|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
59 bytes, text/x-review-board-request
|Details | Review|
https://github.com/whatwg/dom/issues/362 https://github.com/whatwg/dom/pull/489 ErrorEvent is certainly safe to drop, since we only added it in bug 1333901, because the spec didn't indicate that the list had been under discussion for months and was likely to change. :( PopStateEvent is not supported by WebKit in createEvent (according to my testing last November), and we and Blink support it but have no means to initialize it. Edge does support it, with an initializer. IIRC, Telemetry showed ~0 uses, although the telemetry page is taking many minutes to load, so I can't provide a working link right now.
Oh, yes, and foolip intends to try dropping support for these events in Blink as well, and thinks he'll succeed because the usage is very low. https://www.chromestatus.com/metrics/feature/timeline/popularity/1170 https://www.chromestatus.com/metrics/feature/timeline/popularity/1176 PopStateEvent for Chrome is hit by less than 0.000001% of pages.
Comment on attachment 8894608 [details] Bug 1388119 - Drop support for createEvent("ErrorEvent"/"PopStateEvent"); https://reviewboard.mozilla.org/r/165772/#review170858
Attachment #8894608 - Flags: review?(bugs) → review+
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/b668f3429c7f Drop support for createEvent("ErrorEvent"/"PopStateEvent"); r=smaug
Status: ASSIGNED → RESOLVED
Last Resolved: 11 months ago
status-firefox57: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla57
You need to log in before you can comment on or make changes to this bug.