The need to do what was proposed is the same though. Configurability can be arm twisted into submission for things like document and location via accessors, and the WindowProxy can refuse to accept non-configurable properties defined using Object.defineProperty, but that leaves non-configurable bindings created during Top Level Declaration Instantiation that need to be dealt with.
On Sat, Dec 15, 2012 at 12:23 PM, Boris Zbarsky <[email protected]> wrote: > On 12/15/12 12:21 PM, David Bruant wrote: > >> On public-script-coord, Boris Zbarsky showed an example [1] where a >> global variable is var-defined and then observed to be absent from the >> global object it was attached to (because the WindowProxy has changed of >> underlying window object). >> > > No, nothing of the sort. The example shows it _present_ on the global > (the third alert in my example) but missing from the WindowProxy (fourth > alert). > > -Boris > > ______________________________**_________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/**listinfo/es-discuss<https://mail.mozilla.org/listinfo/es-discuss> >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
