PDA

View Full Version : Time to lose the compatibility cruft?



giles
01-04-2010, 12:49 PM
A lot of current WebGL code has code to handle old compatibility problems between the browsers; in particular, I always check for the old context names (webkit-3d/moz-webgl), 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!

Here's the link: http://learningwebgl.com/tests/cruftcheck20100104.html


Cheers,

Giles

lordghost
01-05-2010, 02:12 AM
Test for 20100104 Minefield/3.7a1pre
- Checking WebGL... array types vs Canvas... array types: OK (found WebGLFloatArray)
- Checking context name: OK (got using experimental-webgl)
- Checking parameter getter functions: OK

Test for Chromium 4.0.290.0 (35456)
- Checking WebGL... array types vs Canvas... array types: OK (found WebGLFloatArray)
- Checking context name: OK (got using experimental-webgl)
- Checking parameter getter functions: OK

giles
01-05-2010, 03:56 AM
Thanks, lordghost!