[Webkit-unassigned] [Bug 33696] [dom] let's cache nodelists instead of dynamicnodelist::cache

[bugzilla-daemon at webkit.org]

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





--- Comment #6 from anton muhin <antonm at chromium.org>  2010-01-15 12:26:22 PST ---
(In reply to comment #5)
> (From update of attachment 46659 [details])
> This isn’t just a performance optimization. It’s a behavior change. Caching the
> node list object itself rather than just caching the underlying data means that
> custom JavaScript properties attached by one client will be seen by the other
> client. The client can tell when the cache is flushed by when the property does
> or does not go away. I don’t know if this is desirable, but I do know that we
> need test cases to cover it.
> 
> Please do not land this patch until we explore this issue.

Definitely I won't land it until/if I get r+.

Yes, I understand that's behavior change.  That's exactly the reason why I
wanted to see how it works in FF.

In my understanding w3.org doesn't quite specify if it should be different
objects or the same object, but I am biased here.

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