Proxying window.caches not working
Reported by
arbesf...@gmail.com,
Sep 29 2016
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.116 Safari/537.36 Steps to reproduce the problem: https://jsfiddle.net/nmther6v/ What is the expected behavior? I should be able to access window.caches via a proxy. What went wrong? It threw an error. Did this work before? No Chrome version: 53.0.2785.116 Channel: n/a OS Version: OS X 10.11.4 Flash Version: Shockwave Flash 23.0 r0
,
Oct 4 2016
"VM70:51 Uncaught TypeError: 'get' on proxy: property 'caches' is a read-only and non-configurable data property on the proxy target but the proxy did not return its actual value (expected '#<CacheStorage>' but got '[object Object]')" Is it even intended that it works with window?
,
Oct 4 2016
This is working as intended per spec, see https://tc39.github.io/ecma262/#sec-proxy-object-internal-methods-and-internal-slots-get-p-receiver step 10.a.i. The error message explains pretty clearly what the problem is (and matches up with the informative NOTE in the same bit of the spec).
,
Oct 11 2016
I'm curious if this spec will be visited at any point? I'm looking to proxy host objects in the browser to be able to emulate behavior across sessions.
,
Oct 11 2016
I would recommend filing an issue against the spec, with an explanation of your use case, at https://github.com/tc39/ecma262/issues/ |
|||
►
Sign in to add a comment |
|||
Comment 1 by schenney@chromium.org
, Sep 30 2016