Bug 132705
Summary: | window.screenX can't be cached | ||
---|---|---|---|
Product: | WebKit | Reporter: | Mark Hahnenberg <mhahnenberg> |
Component: | JavaScriptCore | Assignee: | Mark Hahnenberg <mhahnenberg> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | CC: | kling |
Priority: | P2 | ||
Version: | 528+ (Nightly build) | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Bug Depends on: | 132721, 132751, 132916, 132918, 132922 | ||
Bug Blocks: |
Mark Hahnenberg
There are a number of reasons for this.
(1) JSDOMWindow claims HasImpureGetOwnPropertySlot
(2) JSDOMWindow uses setCustom for many of its properties instead of setCacheableCustom.
(3) JSDOMWindow needs to not cache in some cases, even where it says it might be able to. This is dependent on getting rid of HasImpureGetOwnPropertySlot.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Mark Hahnenberg
There are a number of other properties on JSDOMWindow that can't be cached, but I picked screenX as the "canonical example".
Mark Hahnenberg
This is done.