Bug 132705 - window.screenX can't be cached
Summary: window.screenX can't be cached
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Mark Hahnenberg
URL:
Keywords:
Depends on: 132721 132751 132916 132918 132922
Blocks:
  Show dependency tree / graph
 
Reported: 2014-05-08 13:27 PDT by Mark Hahnenberg
Modified: 2014-05-21 11:20 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Hahnenberg 2014-05-08 13:27:41 PDT 
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.
Comment 1 Mark Hahnenberg 2014-05-08 18:01:17 PDT 
There are a number of other properties on JSDOMWindow that can't be cached, but I picked screenX as the "canonical example".
Comment 2 Mark Hahnenberg 2014-05-21 11:20:46 PDT 
This is done.