gecko-dev/dom/animation/test/mochitest.ini

[animation-timeline/test_animation-timeline.html]
skip-if = buildapp == 'mulet'
[css-integration/test_element-get-animation-players.html]
skip-if = buildapp == 'mulet'
[css-integration/test_animations-dynamic-changes.html]
[css-integration/test_animation-effect-name.html]
[css-integration/test_animation-pausing.html]
[css-integration/test_animation-player-playstate.html]
[css-integration/test_animation-target.html]
Bug 998246 part 5 - Add tests for AnimationTimeline; r=dholbert 2014-05-13 11:22:13 +04:00			`[animation-timeline/test_animation-timeline.html]`
Bug 1027242 - Blacklist mulet's failing tests + expose 'mulet' to ini files; fix previous bustage on a CLOSED TREE, r=ahal 2014-07-03 02:40:56 +04:00			`skip-if = buildapp == 'mulet'`
Bug 1032573 part 6 - Add tests for Element.getAnimationPlayers; r=dbaron 2014-07-16 04:02:31 +04:00			`[css-integration/test_element-get-animation-players.html]`
Bug 1027242 - Blacklist mulet's failing tests + expose 'mulet' to ini files; fix previous bustage on a CLOSED TREE, r=ahal 2014-07-03 02:40:56 +04:00			`skip-if = buildapp == 'mulet'`
Bug 1037316 part 1 - Return the same object when updating animations; r=dbaron Previously when updating animations we'd generate a new list of animation objects then try to match up animations from the existing list and copy across state such as start times and notification flags. However, this means that from the API we end up returning different objects. This patch makes us maintain the same object identity when updating an existing animation. It does this by looking for matching animations in both lists. If it finds a match it copies the necessary information from the new animation to the existing animation (but preserving the start time, last notification etc.). Then, finally, it puts the existing animation in the list of new animations and removes the corresponding new animation. The existing animation is also removed from the list of existing animations so that it only matches once. The method used for matching is probably not intuitive but this is addressed in a subsequent patch in this series. 2014-07-23 05:51:12 +04:00			`[css-integration/test_animations-dynamic-changes.html]`
Bug 1045993 part 4 - Add tests for Animation.effect.name; r=dbaron 2014-08-22 16:42:48 +04:00			`[css-integration/test_animation-effect-name.html]`
Bug 1070745 part 9 - Tests for play/pause behavior; r=dholbert 2014-10-20 08:55:45 +04:00			`[css-integration/test_animation-pausing.html]`
Bug 1037321 - Implement playState on AnimationPlayer; r=birtles, r=bz 2014-10-20 08:55:45 +04:00			`[css-integration/test_animation-player-playstate.html]`
Bug 1067701 - Implement Animation.target; r=birtles, r=bz 2014-10-02 10:14:15 +04:00			`[css-integration/test_animation-target.html]`