Colludium , today I get this from firefox:
Chrome & Canary are still the same: Either integer values or 15.99, 17.99 etc... Running your capx with node-webkit also produces the same thing, as expected i guess...
TiAm , it doesn't matter if I run the tests in windowed mode or not. The same thing happen. My Chrome version is 38.0.2125.111 m and it tells me that it's up to date. Canary is 40.0.2208.0 canary (64-bit). I don't know why Chrome doesn't display the 64bit thingy, perhaps it isn't a 64bit version. Is there a normal Chrome 64bit version available...? Anyway, I don't think that has do do anything though.
I don't know what to get out of this, I've even disabled my secondary monitors as was suggested by Tylermon at page 7 and nothing changed on the chrome based browsers. On the other hand, with the secondary monitors disabled, IE11 runs the waterfall benchmark with no scatter what so ever!!!