If a decision is made to return undefined or so in general, also through the prototype chain, my approach obviously won't work. In that case we'll have to think about an alternative that fits the rest of such special properties, like installing an all-can-read api accessor for those properties that return the default value if called from a wrong context.
On Fri, Jul 10, 2015, 19:24 <ad...@chromium.org> wrote: > Just to link discussions together further, the spec-world discussion about > this > is taking place at: > > > https://lists.w3.org/Archives/Public/public-script-coord/2015JulSep/0022.html > > https://codereview.chromium.org/1230793002/ > > -- > -- > v8-dev mailing list > v8-dev@googlegroups.com > 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 v8-dev+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- -- v8-dev mailing list v8-dev@googlegroups.com 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 v8-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
