But obviously it's still visibly different from what Boris suggests, given
that
the property is there.
As I've suggested in another thread, we *could* use all-can-read
interceptors to
achieve both all-can-read and absent, but that's kinda ugly ... We could
support
"invisible" all-can-read accessors that pretend to be absent as long as you
read
it as a regular property, but returns the value returned by the getter when
read
from origin without access. Not exactly sure what's best.
The easiest from our side would be to make the property always be there
(non-deletable) on window.
https://codereview.chromium.org/1230793002/
--
--
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.
