Comments for Dojo 1.3b3 Is Out
The FF3.0 performance backslide is the result of not having a faster-than-DOM branch on FF 3.0 any more. This was a tough call, since the XPath engine was pretty clean and easy to maintain, but we just couldn't afford to include it given the byte budget constratins. Our calculation here is that w/ the imminent release of 3.1...er, 3.5, FF will (on average) be running on the QSA branch more of the time than on the DOM branch. While it does regress compared to 1.2.3, I suspect that 1.3b3 is probably still faster than most other engines on FF 3.0.
Regards
If it slips further, should we just start increasing it by a 0.1 for every month?
;-)
Regards
Wait...ContentPane doesn't have an addChild? That's totally whack. I'll ping Bill about it.
Regards
There are significant speed improvements from 1.2.3 on most browsers, with the exception of Firefox 3 (not 3.1) and Opera 9.
Also it seems the "p:only-child" bug was fixed in 1.3; though there are still issues with the :contians() selector (See "Known Issues")
Currently 1.3b3 does hold the top spot on my "Top Frameworks" graph, but that's because I haven't included a large enough browser sample with the new framework. Though it should give jQuery a run for it's money in speed.
Firefox 3.5 now.
One question, you link to this page...
http://download.dojotoolkit.org/release-1.3.0b3/dojo-release-1.3.0b3/dojo/tests/_base/queryPortability.html
As a demo of "stand alone" query.js, but that page errors out in FF3 and Safari. Is there something else in that page that I'm missing?