core module failure is a bug in WebKit, and it is fixed in ToT, I tested the Safari official release 3.1.2, it fails with the same result, but passes on nightly build r36012.
The second one is a bug in V8 (or Chrome). It returns reversed enumeration order of keys if the object is a literal. Here is a reference to V8 bug: http://code.google.com/p/v8/issues/detail?id=6 var x = [a : 1, b :2]; for (p in x) print(p); It prints out 'b' before 'a'. var x = {}; x.a = 1; x.b = 2; for (p in x) print(p); it prints out 'a' before 'b'; I will take a look at the code. On Sep 2, 12:45 pm, Guyon Morée <[EMAIL PROTECTED]> wrote: > Hi, > > With all the buzz around the new javascript engine in Chrome, I > decided to run the jquery testsuite (http://jquery.com/test/) on my > 3 installed browsers (ff3, ie7 and chrome, on wixp sp3) > > ====================================== > IE7: > > Tests completed in 49734 milliseconds. > 0 tests of 1270 failed. > > FF3: > > Tests completed in 31710 milliseconds. > 0 tests of 1270 failed. > > Chrome: > > Tests completed in 28212 milliseconds. > 2 tests of 1270 failed. > > ====================================== > > Even though, Chrome seems to be a little bit faster than FF and quite > a lot faster than IE, it has 2 failed tests: > > - 64: core module: text(String) (1, 3, 4) > - 112: ajax module: jQuery.param() (1, 3, 4) > > I have really no experience interpreting these results, so I hope > someone here can give me an explaination about these and what it means > to me as a jQuery user. > > Regards, > > guyon
