D
David Mark
That's the hundred dollar question. Never considered such a thing
until I saw this code.
The one that is known to fail in some browsers (not unexpectedly as it
is non-standard?)
Okay, but that won't help for some time (and there still won't be a
reliable fallback).
I think they are just nuts. I wondered what the hell "scope" was
supposed to mean this time (they used to equate that term with the -
this - object).
This is clearly not a good cross-browser design. It's more of the same
Dojo-esque garbage that Google is famous for (and apparently even more
of it this time). Small wonder they start off excluding virtually
every browser in use today except Chrome. Wait a minute, maybe they
aren't so nuts after all.
until I saw this code.
- pass "this" from the global scope to get a reference to it
- use the deprecated someObject.eval in old FireFox (pre 3.0).
The one that is known to fail in some browsers (not unexpectedly as it
is non-standard?)
- In the future, Fx plans to implement closure.environment.eval("x")
for debugging
Okay, but that won't help for some time (and there still won't be a
reliable fallback).
Perhaps something involving manipulation and passing of the arguments
object...
I think they are just nuts. I wondered what the hell "scope" was
supposed to mean this time (they used to equate that term with the -
this - object).
This is clearly not a good cross-browser design. It's more of the same
Dojo-esque garbage that Google is famous for (and apparently even more
of it this time). Small wonder they start off excluding virtually
every browser in use today except Chrome. Wait a minute, maybe they
aren't so nuts after all.