Andrea Giammarchi wrote:
Thanks for the background history, however I am still not sold the fact it's a global object method should mean a global context should be passed.

"Is" (or "was" and therefore "is" because "don't break the web") -- not "ought".

You need a way out of Hume's Guillotine on the Web. I don't know of one. Ideals don't cut it without God-mode powers to rewrite unknown amounts of content. Strict mode could eventually pave a cowpath, but as Mark said, we don't want runtime strictness-testing magic in setTimeout or other builtins.

The point here is that otherWin.setTimeout(func, ...) must -- because of "is" not "ought" -- not pass undefined to func in case it is strict mode, because if it's sloppy and if it is scoped by the current window (not otherWin), then the wrong window will be used.

Is there any point in continuing this thread?

/be
_______________________________________________
es-discuss mailing list
[email protected]
https://mail.mozilla.org/listinfo/es-discuss

Reply via email to