[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 #3 from Adam Barth <abarth at webkit.org>  2010-04-27 14:28:26 PST ---
> A script-test is better:

The problem is we need to wait for the iframe to load.  Can a script test do
that?

> Also.  How do we know that nextNode() and previousNode() are not previously
> acceessed and thus cached (thus making this test a no-op?)

I'm pretty sure nextNode() is fresh.  However, I bet previousNode() is cached. 
I'm not familiar enough with NodeIterator's API to know how to "skip over" a
node so that I can previousNode() back to it and have it be fresh.

> Did you make sure it failed in an earlier version of Safari?

I'll check.

> Why doesn't this need to be waitUntilDone?

Because the load event for the main frame waits for the load event of a the
child iframes and the testing harness waits for the main frame's load event to
fire before ending the test.

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