Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(257)

Side by Side Diff: LayoutTests/fast/dom/Node/fragment-mutation-expected.txt

Issue 23483045: Revert "Switch MutationEvents UseCounter to use countDeprecation." (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Created 7 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
OLDNEW
1 CONSOLE MESSAGE: DOMSubtreeModified is deprecated. Use MutationObservers instead .
2 This test creates a fragment containing three elements: "B", "U", and "P", attem pts to appendChild this fragment and studies effects of mutation events on the f ragment. 1 This test creates a fragment containing three elements: "B", "U", and "P", attem pts to appendChild this fragment and studies effects of mutation events on the f ragment.
3 2
4 Inserting an element in front of the next item in fragment should not affect the result: PASS 3 Inserting an element in front of the next item in fragment should not affect the result: PASS
5 Appending an element at the end of the fragment should not affect the result: PA SS 4 Appending an element at the end of the fragment should not affect the result: PA SS
6 Continually re-appending removed element to the fragment should eventually throw NOT_FOUND_ERR: PASS 5 Continually re-appending removed element to the fragment should eventually throw NOT_FOUND_ERR: PASS
7 6
8 This test creates a fragment containing three elements: "B", "U", and "P", attem pts to insertBefore this fragment and studies effects of mutation events on the fragment. 7 This test creates a fragment containing three elements: "B", "U", and "P", attem pts to insertBefore this fragment and studies effects of mutation events on the fragment.
9 8
10 Inserting an element in front of the next item in fragment should not affect the result: PASS 9 Inserting an element in front of the next item in fragment should not affect the result: PASS
11 Appending an element at the end of the fragment should not affect the result: PA SS 10 Appending an element at the end of the fragment should not affect the result: PA SS
12 Continually re-appending removed element to the fragment should eventually throw NOT_FOUND_ERR: PASS 11 Continually re-appending removed element to the fragment should eventually throw NOT_FOUND_ERR: PASS
13 12
14 13
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698