1917RE: [jslint] option.browser
- Feb 11, 2011I see setTimeout (and cousins) are still in the browser defined list, but
would you recomend the same rule of thumb be true for these? E.g. would you
recommend "window.setTimeout( func...." rather than "setTimeout( func...."?
From: email@example.com [mailto:firstname.lastname@example.org] On
Behalf Of douglascrockford
Sent: Friday, February 11, 2011 8:17 AM
Subject: [jslint] option.browser
The browser predefinition list has gotten a lot shorter:
/*global clearInterval: false, clearTimeout: false,
document: false, event: false, frames: false,
history: false, Image: false, location: false,
name: false, navigator: false, Option: false,
parent: false, screen: false, setInterval: false,
setTimeout: false, XMLHttpRequest: false */
The window.* methods and related properties have been removed.
It is generally a bad idea to be poking at the window object,
but if you must, do it explicitly. Write
because the implicit form fails in strict mode. When a function is called as
a function, this will be bound to undefined. In sloppy mode, this was bound
to the global object, which was a bad idea, which enabled the implicit form,
which was also a bad idea.
- << Previous post in topic Next post in topic >>