RESOLVED FIXED 132705
window.screenX can't be cached 
https://bugs.webkit.org/show_bug.cgi?id=132705
Summary window.screenX can't be cached
Mark Hahnenberg
Reported 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.
Attachments
Add attachment proposed patch, testcase, etc.
Mark Hahnenberg
Comment 1 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".
Mark Hahnenberg
Comment 2 2014-05-21 11:20:46 PDT
This is done.
Note You need to log in before you can comment on or make changes to this bug.