Closed Bug 1952410 Opened 15 days ago Closed 7 days ago

Keep enable the DOM mutation events when we run crash tests of the editor until it's shipped in release

Categories

(Core :: DOM: Editor, task)

task

Tracking

()

RESOLVED FIXED
138 Branch
Tracking Status
firefox138 --- fixed

People

(Reporter: masayuki, Assigned: masayuki)

References

Details

Attachments

(1 file)

We have added a lot of crash tests of the editor which detects unexpected situations after touching the DOM from the editor module. Some of them may cause security issues. So, until we ship disabling the DOM mutation events in the release channel, we should keep testing them even in the nightly channel to detect regressions immediately.

[Tracking Requested - why for this release]:

Flags: sec-bounty?

We added a lot of crash tests for tricky cases for the editor module. Some of
them use the legacy DOM mutation events, and some of them caused serious issues.

Thus, we should enable the DOM mutation events at least running the tests to
detect regressions as soon as possible.

Flags: sec-bounty?
Pushed by masayuki@d-toybox.com: https://hg.mozilla.org/integration/autoland/rev/1ec3b9a31429 Enable DOM mutation events when running crash tests for the editor module until it's disabled in the release channel r=smaug,m_kato
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/51345 for changes under testing/web-platform/tests
Status: ASSIGNED → RESOLVED
Closed: 7 days ago
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
Upstream PR merged by moz-wptsync-bot
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: