[Webkit-unassigned] [Bug 49501] Removing an HTML node causes an earlier(!!) query to not see it

[bugzilla-daemon at webkit.org]

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





--- Comment #3 from Evan Martin <evan at chromium.org>  2010-11-13 15:49:00 PST ---
Created an attachment (id=73836)
 --> (https://bugs.webkit.org/attachment.cgi?id=73836&action=review)
better demo

Here's a better example, where we flip a coin to decide whether to remove the node or not.  Load this, bring up the console, repeatedly hit f5 and boggle at the first line of output changing.

I guess something is printing the actual value of getElementsByTagName too late -- we always seem to successfully get the first node, whether or not the console.log thinks it exists.

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