The named property visibility algorithm has got changed in the spec. |
|||||||||
Issue descriptionhttps://github.com/heycam/webidl/issues/152 got closed with agreement to change the order of property look-up. The spec[1] got updated accordingly. V8 needs to follow the change accordingly. [1] http://heycam.github.io/webidl/#dfn-named-property-visibility The new order of property look-up is as follows: 1. Indexed properties. 2. Own properties, including unforgeable attributes and operations. 3. Then, if [OverrideBuiltins]: 3-1. Named properties. 3-2. Properties from the prototype chain. 4. Otherwise, if not [OverrideBuiltins]: 4-1. Properties from the prototype chain. 4-2. Named properties.
,
Sep 16 2016
,
Sep 16 2016
If prototype chains wouldn't be first-class, yes. But no, we can't work around it like that.
,
Nov 8 2016
,
Jul 17 2017
,
Aug 8 2017
Is this a V8 internals, V8 API, or Blink Bindings bug? Whichever it is the current component doesn't look right.
,
Aug 9 2017
cbruni@, could you set a right component, or move the issue to crbug.com/v8?
,
Aug 9 2017
,
Aug 9
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 14
,
Aug 20
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by jochen@chromium.org
, Sep 16 2016