Nice, subtle differencies of Javascript language implementation between Mozilla-like and Explorer.

First one: this statement is legal in Mozilla:

var a = {el1: 1, el2: 2,}

Whereas in explorer must be changed to (notice the trailing ‘,’ removed):

var a = {el1: 1, el2: 2}

Then; this is legal in Mozilla:

var a = this.options.class;

Whereas in Explorer you must:

var a = this.options[’class’];

I’m not saying ‘explorer is guilty’ because, in fact, I don’t know which one variant is legal. Anyway: grrrr >_<

Posted by mattia as ajax, ecmascript, explorer, javascript at 4:18 PM CET

No Comments »

Really, you shouldn’t mix the two things. I discovered today that, with firebug activated, writing to a document opened this way just produced big problems with inclusions of javascripts and CSS (just three out of 20+ was really included).

Did I already say “sigh, open source!”?

Posted by mattia as ajax, firebug, firefox, javascript at 4:06 PM CEST

No Comments »

Substantially, this has made me mad. In the current status, you can’t reliably use getElementById on objects returned by an XMLHttpRequest. Useless to say, there’s a way to make things work correctly, but only under Firefox. Sigh.

Posted by mattia as ajax, ecmascript, html, xml at 2:19 PM CEST

No Comments »