Summary: | JSDOMWindow should not claim HasImpureGetOwnPropertySlot | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Mark Hahnenberg <mhahnenberg> | ||||
Component: | JavaScriptCore | Assignee: | Mark Hahnenberg <mhahnenberg> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | cdumez, cgarcia, commit-queue | ||||
Priority: | P2 | ||||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Bug Depends on: | |||||||
Bug Blocks: | 132705 | ||||||
Attachments: |
|
Description
Mark Hahnenberg
2014-05-14 11:51:54 PDT
Created attachment 231536 [details]
Patch
Comment on attachment 231536 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=231536&action=review r=me > Source/WebCore/ChangeLog:12 > + We now correctly handle the impurity of JSDOMWindow's custom getOwnPropertySlot without needing the > + blanket HasImpureGetOwnPropertySlot. Getting rid of this flag will allow us to cache many Should specify that we do this through explicit watchpoint. Committed r168914: <http://trac.webkit.org/changeset/168914> Comment on attachment 231536 [details]
Patch
Clearing review flag.
|