I never knew any of all that stuff you have all mentioned, and as an end user, I don't think I would ever need to know. To me, I use `window` as a global object, and it has never been more than that.
I've never written any sort of code that can prove or verify any of what you all are talking about. Mind showing code samples? If a sample of code isn't possible, or if to the end user there's really just some single global object as far as their code is concerned, then "global object" is in fact a good name. That's why I'd like to see how what has been said actually manifests itself in end-user code. On Sun, Oct 6, 2019 at 1:43 PM Boris Zbarsky <[email protected]> wrote: > > On 10/6/19 2:58 PM, Raul-Sebastian Mihăilă wrote: > > Also let's not forget that the WindowProxy behavior contradicts the JS > > object model in that the non-configurable 'something' own property of > > the window proxy is removed. > > There is a proposal for addressing that. Firefox has been shipping it > in Nightly for a while, but we have seen zero interest from any other > browsers for addressing that issue... > > See https://github.com/tc39/ecma262/pull/688#issuecomment-430648819 and > following comments for the details of the proposal. > > -Boris > _______________________________________________ > es-discuss mailing list > [email protected] > https://mail.mozilla.org/listinfo/es-discuss _______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
