JavaScript Objects and Proxies
The cluster focuses on JavaScript's object model quirks, including prototype chain issues, property access pitfalls, and solutions like ES6 Proxies and Crockford objects.
Activity Over Time
Top Contributors
Keywords
Sample Comments
See "Crockford Objects" here for example: https://levelup.gitconnected.com/crockford-objects-in-javasc...
There's still Proxy for that.https://developer.mozilla.org/en/docs/Web/JavaScript/Referen...
This is coming in ES6, with Proxies.
ES6 will add proxies, another approach.
Objects in JavaScript are just maps, so technically speaking if they disallow "this[#foo]", it's just a cheap trick.
They're probably talking about the fact that it also works on objects (JS equivalent of dicts)
Proxies and state-mutating getter functions are pretty edge features of JS tbh
And god help you if you've extended the Array or Object prototypes.
No current browser should be vulnerable to this (ES5 requires object literals use [[DefineOwnProperty]], not [[Put]], and hence no setter on the prototype chain should be called). I believe all browsers have since fixed this.
Goodbye object literals too, apparently.