xoxxxoxooxox

Although this does solve the problem, doesn't the default behavior of chrome undermine the predictability (or reliability?) of WebGL as an API? This is reminiscent of old OpenGL era except that now behavior is altered by the browsers rather than the drivers themselves.

Two different WebGL implementations (chrome on the left, firefox on the right) working side by side on Linux x64. Note the subtle difference in colors.