Updates:
Status: WontFix
Cc: [email protected] [email protected]
Comment #1 on issue 4321 by [email protected]:
Object.prototype.__lookupGetter__ returns getter from prototype even if
there's an own property with a value set (regression?)
https://code.google.com/p/v8/issues/detail?id=4321
Note: The 4.2 branch is dead; however this detail hasn't changed since.
This appears to have changed in https://codereview.chromium.org/467293003.
The old code indicates that the behavior you expect was specific to
*read-only* properties present on the receiver (or anywhere on the
prototype chain before the getter, really); so at least unifying that to be
the same for writable and non-writable properties seems like a good idea.
Since there is no spec for __lookupGetter__, it's hard to say which
behavior (returning 'undefined', or looking past the data property to the
getter) is "correct". Since the change happened a year ago, reverting it
now seems at least as risky as just leaving it.
I suggest you simply stop using __lookupGetter__.
Closing as WontFix until more evidence turns up to suggest that some action
is required here.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
