no introspection or nothing magic and weird, simply `.call(undefined)` would do for sloppy and strict, preserving global in sloppy, avoiding shenanigans in strict.
Hence my curiosity: when this experiment was made, which code with `"use strict"` failed ? 'cause that would be the only one that either was working "by accident" polluting a global context or the use case I am asking/looking for. Regards On Mon, Sep 8, 2014 at 12:16 PM, Boris Zbarsky <[email protected]> wrote: > On 9/8/14, 3:50 AM, Andrea Giammarchi wrote: > >> I wonder what was breaking >> > > I don't remember, unfortunately. :( > > specially after showing there were >> inconsistencies between browsers. >> > > It's worth asking the IE team whether they changed because of concrete web > compat issues or just to align with the spec and other browsers. > > Yet nobody wrote a use case where a >> dev explicitly marks a callback as strict >> > > It doesn't matter. The web compat constraint, if any, would be with > sloppy callbacks. If the callback expects a "this" object other than its > global, the caller needs to pass it explicitly. Unless you want callers > introspecting the strictness of the callee before deciding on what to do > with "this"... but that seems pretty weird too. > > Curious to know if ES5 at that time was popular. >> > > I don't know what you mean here. > > -Boris >
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
