We should try to get rid of mutation events ASAP. In order to do so, we need an unprefixed alternative. Mozilla is removing the prefix in https://bugzilla.mozilla.org/show_bug.cgi?id=749920 so we should do the same after making sure our implementation matches the spec. As far as I know, the bug 83496 is the only blocker for this bug for ports that use V8. For ports that use JSC, we also need to fix bug 71865 and bug 78290.
(In reply to comment #0) > We should try to get rid of mutation events ASAP. In order to do so, we need an unprefixed alternative. > > Mozilla is removing the prefix in https://bugzilla.mozilla.org/show_bug.cgi?id=749920 so we should do the same after making sure our implementation matches the spec. > > As far as I know, the bug 83496 is the only blocker for this bug for ports that use V8. For ports that use JSC, we also need to fix bug 71865 and bug 78290. Just marked 83496 as a dup (it was fixed in bug 83706), and bug 71865 was fixed in http://trac.webkit.org/changeset/107008, so the only difference in behavior I know of between WebKit and Mozilla is due to bug 78290 (only affecting JSC-using ports, it boils down to a lack of proper timing for DOM mutations due to editing).
A correction: bug 78290 affects not just non-V8 ports, but any non-Chromium port.
Found a major interoperability difference between the WebKit and Firefox implementations: FF notifies of mutations done by the parser. We'll want to resolve that before unprefixing. See bug 89351.
This happened at some point, except for the warning for mutation events. That probably warrants a new bug at this point though if we want to pursue it.