Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

WebGL malfunction in latest version

  • 1 个回答
  • 1 人有此问题
  • 3 次查看
  • 最后回复者为 stegu

more options

I have a GLSL tutorial at this address: http://www.itn.liu.se/~stegu/OpenGLinsights/shadertutorial.html With the update to Android 4 and the latest version of Firefox, shaders 5 to 10 stopped working correctly. Everything was fine before, and looked like the desktop version. I really want this to work on FF for Android, but the bug is silent (fatal malfunction without any error message) even though I think I did everything to spec, and like I said, things were fine before the update. Any hints to whether this is a bug or an error on my part? My platform is Android 4 on a Samsung Galaxy Note (N7000). I have no other WebGL capable mobile platform to test this.

I have a GLSL tutorial at this address: http://www.itn.liu.se/~stegu/OpenGLinsights/shadertutorial.html With the update to Android 4 and the latest version of Firefox, shaders 5 to 10 stopped working correctly. Everything was fine before, and looked like the desktop version. I really want this to work on FF for Android, but the bug is silent (fatal malfunction without any error message) even though I think I did everything to spec, and like I said, things were fine before the update. Any hints to whether this is a bug or an error on my part? My platform is Android 4 on a Samsung Galaxy Note (N7000). I have no other WebGL capable mobile platform to test this.

所有回复 (1)

more options

I have routed around the bug in this somewhat crippled version: http://www.itn.liu.se/~stegu/OpenGLinsights/shadertutorial_mobile.html Still no solution to the original problem, and still no clue to what is wrong. The shader runs, but shows a completely wrong and glitchy pattern. Works fine on desktop version, worked fine in Android 2.3 on the same phone and with the same version of FF.