"use strict" VS setTimeout
brendan at mozilla.org
Mon Sep 8 16:10:40 PDT 2014
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
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
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?
More information about the es-discuss