Implement in two browsers #14
Comments
I think the Chromium patch covers the "Behind a flag" check too. |
Sure, I'll just check that off once it lands in Canary. |
Nit: It’s V8, not “v8”. |
For record sake, I've filed a Firefox bug/request: https://bugzilla.mozilla.org/show_bug.cgi?id=1245024 |
@mathiasbynens fixed (altho that's sad, i really prefer the lowercase v aesthetically) |
landed in WebKit last night: https://webkit.org/b/153799 / https://webkit.org/b/153814 |
thanks @caitp is it behind a flag or enabled by default? |
It's on by default |
👍 |
@caitp Awesome!! |
Linking to tc39/ecma262#593 (comment) since this feature's spec changed slightly in July 2016. |
anything the polyfill should consider? I'm not sure I understand |
@WebReflection EG, if Object.getOwnPropertyDescriptor returns undefined for a name, it is not added to the result object |
I've got the idea behind, yet I don't know how that would be possible. Can you define a property without a descriptor? Any example in order to reproduce with a test and eventually update my code? Thanks |
You can (under some conditions) lie about the properties a Proxy has.
We don't throw an exception for lying about property keys in this case, because invariants are not violated, so it's possible to get an undefined descriptor into the algorithm. |
or in a polyfill this might look like
|
got it, thanks |
@WebReflection the polyfill is updated in ljharb/Object.getOwnPropertyDescriptors@fc060fc - i updated the reference implementation in c13d24e as well (thanks for the reminder). |
In order to progress to stage 4, this proposal must be implemented in two stable browsers, not behind any flags.
Implemented:
At least behind a flag:
Shipped stable:
The text was updated successfully, but these errors were encountered: