Chrome Version: 59 canary
OS: All but iOS

What steps will reproduce the problem?
(1) Open http://w3c-test.org/dom/nodes/MutationObserver-document.html

What is the expected result?
No FAIL tess

What happens instead?
One FAIL test.

Please use labels and text to provide additional information.

DOM mutations in the failing test is:

<p id='n00'></p><script id='s002'>
  var newScript = document.createElement("script");
  setupTest.step(function() {
    newScript.textContent = "document.body.appendChild(newElement);";
    newScript.id = "inserted_script";
    document.getElementById("n00").appendChild(newScript);

Expected MutationRecords are:

                       [{type: "childList",
                         addedNodes: function () {
                           return [ document.getElementById("inserted_script") ];
                         },
                         target: function () {
                          return document.getElementById("n00");
                         }},
                        {type: "childList",
                         addedNodes: function () {
                           return [ document.getElementById("inserted_element") ];
                         },
                         previousSibling: function () {
                           return document.getElementById("s002");
                         },
                         target: document.body}
                        ]

However, the order of MutaionRecords are reversed in Chromium browser.