Magic-Mirror/gecko-dev
1
0
Fork 0
mirror of https://github.com/mozilla/gecko-dev.git synced 2024-10-12 04:45:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Bug 1194037 part 6 - Add test for order of mutation observer records; r=heycam

Browse Source
This commit is contained in:
Brian Birtles 2015-09-11 15:02:04 +09:00
parent 19376b1e45
commit fa52a070ee
1 changed files with 66 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

66
dom/animation/test/chrome/test_animation_observers.html
View File

@ -737,6 +737,72 @@ function assert_records(expected, desc) {
});
});
addAsyncAnimTest("tree_ordering", { observe: div, subtree: true }, function*() {
// Create a tree with two children:
//
// div
// / \
// childA childB
var childA = document.createElement("div");
var childB = document.createElement("div");
div.appendChild(childA);
div.appendChild(childB);
// Start an animation on each (using order: childB, div, childA)
//
// We include multiple animations on some nodes so that we can test batching
// works as expected later in this test.
childB.style = "animation: anim 100s";
div.style = "animation: anim 100s, anim 100s, anim 100s";
childA.style = "animation: anim 100s, anim 100s";
var divAnimations = div.getAnimations();
var childAAnimations = childA.getAnimations();
var childBAnimations = childB.getAnimations();
// The order in which we get the corresponding records is currently
// based on the order we visit these nodes when updating styles.
//
// That is because we don't do any document-level batching of animation
// mutation records when we flush styles. We may introduce that in the
// future but for now all we are interested in testing here is that the order
// these records are dispatched is consistent between runs.
//
// We currently expect to get records in order childA, childB, div
yield await_frame();
assert_records([{ added: childAAnimations, changed: [], removed: [] },
{ added: childBAnimations, changed: [], removed: [] },
{ added: divAnimations, changed: [], removed: [] }],
"records after simultaneous animation start");
// The one case where we *do* currently perform document-level (or actually
// timeline-level) batching is when animations are updated from a refresh
// driver tick. In particular, this means that when animations finish
// naturally the removed records should be dispatched according to the
// position of the elements in the tree.
//
// Fast-forward to *just* before the end of the animation.
var fastForward = animation => animation.currentTime = 99999;
divAnimations.forEach(fastForward);
childAAnimations.forEach(fastForward);
childBAnimations.forEach(fastForward);
yield await_event(div, "animationend");
// We should get records in order div, childA, childB
assert_records([{ added: [], changed: [], removed: divAnimations },
{ added: [], changed: [], removed: childAAnimations },
{ added: [], changed: [], removed: childBAnimations }],
"records after finishing");
// Clean up
div.style = "";
childA.remove();
childB.remove();
});
// Run the tests.
SimpleTest.waitForExplicitFinish();