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 »
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 »
You know that there will never exist a single language to control everything when you start writing stuff like this:
<body tal:attributes=”onload python:’javascript:fill_form(%d);;’ % p[’uid’]”>
I mean, four programming/markup languages in one row it’s quite the best I’ve succeeded in for something meaningful.
(for the curious, I’m talking about markup XHTML, markup/programming TAL, programming python and javascript, or better ECMAScript).
Posted by mattia as ecmascript, python, xhtml, zpt at 9:26 PM CEST
No Comments »
