[UPDATE 23 August 2010: one of the API changes this post is talking about, from CanvasFloatArray to WebGLFloatArray, was itself superseded by a change to Float32Array later on. The test page here is no longer relevant -- it will fail saying that it can't find the canvas array types]
[This is a cross-post from the WebGL forums.]
A lot of current WebGL pages, including the ones on this site, have code to handle old compatibility problems between the browsers; in particular, I always check for the old context names, the CanvasFloatArray/WebGLFloatArray move, and the move from getShaderi to getShaderParameter.
It looks like these checks might now be unnecessary; checking Firefox and the Chrome dev channel, it looks like both of them use the current spec for all three of these. In general, Safari seems to be ahead of the others when it comes to spec compliance, so it’s *probably* sorted too…
However, I’ve only checked on a PC, and it would be really interesting to hear what everyone else sees — in particular people using Macs and Linux. I’ve put together a page that checks browsers for the three changes above; test results would be much appreciated!
To check your browser, go to this page. Copy and paste the results, and put them in a comment here along with your OS and browser details. I’ll post with the aggregated results in a day or so.