Bugzilla – Bug 582
Add test checking that getProgramInfoLog returns a string
Last modified: 2012-01-26 12:55:01 PST
We seem to be missing a test checking that the return value of getProgramInfoLog is a string. The WebGL spec doesn't say anything special about getProgramInfoLog, but it returns a DOMString so it's unexpected for it to return null. Chromium sometimes returns null instead of a (possibly empty) string: http://code.google.com/codesearch#OAMlx_jo-ck/src/content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc&exact_package=chromium&type=cs&l=796 We have come across a practical application that didn't run because of that.
See http://code.google.com/p/chromium/issues/detail?id=111337
Created attachment 98 [details] Check that the infolog is a string We should also check if similar tests are needed for other string-returning functions such as getShaderInfoLog.
Hm, Chromium does pass this test here (does return empty strings). I wonder how to hit the case in http://code.google.com/codesearch#OAMlx_jo-ck/src/content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc&exact_package=chromium&type=cs&l=796
(In reply to comment #3) > Hm, Chromium does pass this test here (does return empty strings). I wonder how > to hit the case in > > http://code.google.com/codesearch#OAMlx_jo-ck/src/content/renderer/gpu/webgraphicscontext3d_command_buffer_impl.cc&exact_package=chromium&type=cs&l=796 I'm told that this is because I'm on Linux and this bug only occurs on Windows and Mac.
Fixed in r16739, r16741, r16742.