Add a pref to stop running the paths for supporting legacy mutation events in the editor module
Categories
(Core :: DOM: Editor, task)
Tracking
()
People
(Reporter: masayuki, Unassigned)
References
Details
The editor module has a lot of DOM tree check after touching the DOM because a legacy DOM mutation event listener may modify the DOM immediately. Now, the legacy DOM mutation events are disabled in the all channels. However, I'm not 100% sure that it's safe to remove the editor code for supporting the legacy DOM mutation events because they might avoid to crash or something insecure situations which may be caused by a synchronous event dispatching. E.g., if an element which may load a content like <img> is inserted or deleted, an error event or something may be dispatched synchronously. In such case, we need to change the dispatcher to the async one or keep maintaining the editor's code.
So, my plan is, add a pref to disable the editor code for supporting the legacy DOM mutation events. Then, I'll request fuzzing team to enable it when they run fuzzing tests. Finally, list up the found issues and fix or consider to keep the editor code for each case.
Description
•