[Webkit-unassigned] [Bug 38219] Add test for NodeIterator behavior change from removing custom bindings

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=38219





--- Comment #2 from Eric Seidel <eric at webkit.org>  2010-04-27 14:23:41 PST ---
(From update of attachment 54455)
A script-test is better:

script-tests/node-iterator-prototype.js:

description("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.")

function runTest() {
    shouldBeEqualToString("it.nextNode().foo", "child");
    shouldBeEqualToString("it.previousNode().foo", "child");
}

Node.prototype.foo = "parent"

var iframe = document.createElement("iframe");
iframe.onload = "runTest()";
frame.src = "resources/node-iterator-prototype-frame.html";
document.body.appenChild(iframe);


Also.  How do we know that nextNode() and previousNode() are not previously
acceessed and thus cached (thus making this test a no-op?)  Did you make sure
it failed in an earlier version of Safari?

Why doesn't this need to be waitUntilDone?

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.