Half or more compatibility issues caused by unexpected DOM change by
web apps. However, it's difficult to investigate the web apps' source
code because they are usually minified. Therefore, I usually debug
the unexpected behavior with C++ debugger and adding break points into
`HTMLEditor`.
For saving the debug time and helping developers to understand what's
going on, `HTMLEditor` should log when it touches the DOM and when
unexpected DOM change occurs.
Differential Revision: https://phabricator.services.mozilla.com/D260589
This also renames `OnDocumentModified()` to
`RunOrScheduleOnModifyDocument()` because the name is usually confused
with `OnModifyDocument().
Differential Revision: https://phabricator.services.mozilla.com/D260588
This reverts commit 73d1ab198c.
Revert "Bug 1973655 - part 2: Make `HTMLEditorMutationObserver.cpp` r=m_kato"
This reverts commit 8603a23c33.
Revert "Bug 1973655 - part 1: Make the editor module not call DOM API to modify the DOM directly r=m_kato"
This reverts commit a8abe8d84c.
Half or more compatibility issues caused by unexpected DOM change by
web apps. However, it's difficult to investigate the web apps' source
code because they are usually minified. Therefore, I usually debug
the unexpected behavior with C++ debugger and adding break points into
`HTMLEditor`.
For saving the debug time and helping developers to understand what's
going on, `HTMLEditor` should log when it touches the DOM and when
unexpected DOM change occurs.
Differential Revision: https://phabricator.services.mozilla.com/D260589
This also renames `OnDocumentModified()` to
`RunOrScheduleOnModifyDocument()` because the name is usually confused
with `OnModifyDocument().
Differential Revision: https://phabricator.services.mozilla.com/D260588
Sylvestre Ledru