The current developer build of Chrome/Chromium has hardware acceleration (switch enabled). The 3.7 developer build of Firefox also has it (and it's supposed to be faster than IE9). Why didn't they compare those, since IE9 is also a developer build?
They can test against whatever they want, but the fact still remains that IE9 is basically using 'specialized hardware' to reach that speed. What happens when Chrome also supports this specialized hardware? [i.e. I hope that the IE Team doesn't feel like they can skimp on performance elsewhere by just throwing hardware at the problem, rather than fixing/improving their engine.]
No it isn't. Firefox in software mode (release builds) is generally faster than Chrome when it comes to canvas. Firefox in hardware mode (pre-release, Direct2D) is around as fast as IE.
Comments
Chrome is currently the fastest at this; what else would you have them test against?
The current developer build of Chrome/Chromium has hardware acceleration (switch enabled). The 3.7 developer build of Firefox also has it (and it's supposed to be faster than IE9). Why didn't they compare those, since IE9 is also a developer build?
Chrome's acceleration is not of the entire page. It is only acceleration of things like 3D transforms and a few other things.
They can test against whatever they want, but the fact still remains that IE9 is basically using 'specialized hardware' to reach that speed. What happens when Chrome also supports this specialized hardware? [i.e. I hope that the IE Team doesn't feel like they can skimp on performance elsewhere by just throwing hardware at the problem, rather than fixing/improving their engine.]
Chrome is currently the fastest at this
No it isn't. Firefox in software mode (release builds) is generally faster than Chrome when it comes to canvas. Firefox in hardware mode (pre-release, Direct2D) is around as fast as IE.