LayoutTests/traversal/node-iterator-prototype-expected.txt - Issue 14146002: Remove all generic expected results for which a generic Chromium expected result exists

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: LayoutTests/traversal/node-iterator-prototype-expected.txt

Issue 14146002: Remove all generic expected results for which a generic Chromium expected result exists (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Created 7 years, 8 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 side-by-side diff with in-line comments

Download patch

« no previous file with comments | « LayoutTests/transitions/cross-fade-border-image-expected.txt ('k') | LayoutTests/userscripts/window-onerror-for-isolated-world-1-expected.txt » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/traversal/node-iterator-prototype-expected.txt

diff --git a/LayoutTests/traversal/node-iterator-prototype-expected.txt b/LayoutTests/traversal/node-iterator-prototype-expected.txt

deleted file mode 100644

index 588bc87c778bcc4c0ea2f520495bdf198b7c1a56..0000000000000000000000000000000000000000

--- a/LayoutTests/traversal/node-iterator-prototype-expected.txt

+++ /dev/null

@@ -1,11 +0,0 @@

-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: parent FAIL

-B: parent FAIL

-C: parent FAIL

-D: parent FAIL