Why not 'jslint' your javascript. If I encounter any strange behaviour
it's the first thing I do.
Chad schreef:
The most annoying thing about "the bug" in IE is the silent failure.
My simple test above doesn't even give you an error. It just sits
there silently. The problem gets a lot worse when you have 500 line
javascript files and there errors show up in places that don't make
sense
On Feb 14, 4:51 am, Michal Charemza <[email protected]> wrote:
Looking at the Ecmascript 262 Edition 3 standard (p53), although I
might be misunderstanding it, it does indeed appear that this is a
Firefox bug. (I hate it when that happens).
*However* looking athttp://wiki.ecmascript.org/doku.php?id=proposals:bug_fixes
, it looks like the trailing comma issue seen as a bug in the
standard itself, to be fixed in a later edition of the language. So
Firefox is almost right ;-)
(By the way, I might be getting confused between the Javascript/
Ecmascript relationship: sorry if I am)
On 14 Feb 2009, at 12:25, Tom Occhino wrote:
Not an IE bug, a Firefox bug. The code is incorrect with a trailing
comma.
On Feb 13, 2009, at 1:21 PM, Chad wrote:
Thanks for the quick response.. I didn't realize it was an IE bug.
Lame
On Feb 13, 11:52 am, Michal Charemza <[email protected]>
wrote:
On 13 Feb 2009, at 19:50, Chad wrote:
However, if I remove the comma all the sudden it starts working..
The comma thing is a standard IE bug, and common to all Javascript.
Any object defined as
{
key1: value1,
key2: value2
}
*Must not* have a comma after the final value, otherwise IE just
dies.
Michal.
