Reviewed by Tony Chang.
[Chromium] traversal/node-iterator-prototype.html has incorrect baselines
https://bugs.webkit.org/show_bug.cgi?id=46413
Chromium/V8 actually gets this test right (unlike JSC), but had
incorrect baselines for it checked in by r58524.
* platform/chromium-mac/traversal/node-iterator-prototype-expected.txt: Removed.
* platform/chromium-win/traversal/node-iterator-prototype-expected.txt: Removed.
* platform/chromium/test_expectations.txt:
* platform/chromium/traversal/node-iterator-prototype-expected.txt: Added.
git-svn-id: http://svn.webkit.org/repository/webkit/trunk@68208
268f45cc-cd09-0410-ab3c-
d52691b4dbfc
+2010-09-23 Mihai Parparita <mihaip@chromium.org>
+
+ Reviewed by Tony Chang.
+
+ [Chromium] traversal/node-iterator-prototype.html has incorrect baselines
+ https://bugs.webkit.org/show_bug.cgi?id=46413
+
+ Chromium/V8 actually gets this test right (unlike JSC), but had
+ incorrect baselines for it checked in by r58524.
+
+ * platform/chromium-mac/traversal/node-iterator-prototype-expected.txt: Removed.
+ * platform/chromium-win/traversal/node-iterator-prototype-expected.txt: Removed.
+ * platform/chromium/test_expectations.txt:
+ * platform/chromium/traversal/node-iterator-prototype-expected.txt: Added.
+
2010-09-23 Andrew Wilson <atwilson@chromium.org>
Unreviewed, rolling out r68197.
+++ /dev/null
-This test checks whether DOM wrappers created by NodeIterator have their prototypes attached to the correct objects. These nodes are from the child frame, so that's where their prototypes should be attached.\r
-\r
-Unfortunately, our implementation is buggy and we get wrappers from the parent frame here. This test documents the bug so we'll know when we fix it.\r
-\r
-test: child PASS\r
-A: child PASS\r
-B: child PASS\r
-C: child PASS\r
-D: child PASS\r
-D: child PASS\r
-This test checks whether DOM wrappers created by NodeIterator have their prototypes attached to the correct objects. These nodes are from the child frame, so that's where their prototypes should be attached.\r
-\r
-Unfortunately, our implementation is buggy and we get wrappers from the parent frame here. This test documents the bug so we'll know when we fix it.\r
-\r
-test: child PASS\r
-A: child PASS\r
-B: child PASS\r
-C: child PASS\r
-D: child PASS\r
-D: child PASS\r
BUGWK38360 WIN LINUX SKIP : fast/images/svg-background-partial-redraw.html = TEXT
BUGWK38360 WIN LINUX SKIP : svg/carto.net/tabgroup.svg = TEXT
-// Needs updated Chromium baselines
-BUGMIHAIP : traversal/node-iterator-prototype.html = TEXT
-
BUG42895 : media/audio-only-video-intrinsic-size.html = TIMEOUT
BUG42895 : media/media-document-audio-size.html = TIMEOUT
BUGYAAR MAC : svg/custom/dominant-baseline-hanging.svg = MISSING
C: child PASS
D: child PASS
D: child PASS
-This test checks whether DOM wrappers created by NodeIterator have their prototypes attached to the correct objects. These nodes are from the child frame, so that's where their prototypes should be attached.
-
-Unfortunately, our implementation is buggy and we get wrappers from the parent frame here. This test documents the bug so we'll know when we fix it.
-
-test: child PASS
-A: child PASS
-B: child PASS
-C: child PASS
-D: child PASS
-D: child PASS