User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b7) Gecko/20100101 Firefox/4.0b7 Build Identifier: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0b8pre) Gecko/20101123 Firefox/4.0b8pre There is tearing in the Aquarium WebGL demo. (In reply to https://bugzilla.mozilla.org/show_bug.cgi?id=603367#c13) > This tearing is an artifact of the demo itself when its textures haven't > finished loading. Normally if you give it some more time it ends up rendering > correctly. It has been running like 30 minutes now and it still looks torn. Reproducible: Always Actual Results: http://img148.imageshack.us/img148/791/aquariumminefield.png On Minefield. Expected Results: http://img403.imageshack.us/img403/3638/aquariumchrome.png On Chrome. Radeon HD 4650 Catalyst 10.11 driver

Weird, I don't get this problem with my NVIDIA card. Can you go to about:config, enable webgl.verbose, rerun, open the JS error console (ctrl+shift+J) and let me know if there's any WebGL warning there?

These warnings are in the error console: Warning: Error in parsing value for 'filter'. Declaration dropped. Source File: http://webglsamples.googlecode.com/hg/jquery-ui-1.8.2.custom/css/ui-lightness/jquery-ui-1.8.2.custom.css Line: 18 (6 of these warnings ^) Warning: Unknown property 'zoom'. Declaration dropped. Source File: http://webglsamples.googlecode.com/hg/jquery-ui-1.8.2.custom/css/ui-lightness/jquery-ui-1.8.2.custom.css Line: 303 (8 of these warnings ^) No WebGL warnings.

I can confirm this with Seamonkey trunk and an nvidia 310m on win7. I think It appeared after I installed the latest driver a month ago to stop driver crashes. Adapter DescriptionNVIDIA GeForce 310M Vendor ID10deDevice ID0a75Adapter RAM512Adapter Driversnvd3dum nvwgf2um,nvwgf2umDriver Version8.17.12.6089Driver Date10-8-2010Direct2D EnabledtrueDirectWrite EnabledtrueGPU Accelerated Windows6/6 Direct3D 10

Given that this most likely isn't a bug on our part but rather either a driver issue or an issue in this demo, and given that it only results in poor rendering in this demo, I wouldn't block on this.

The demo is rendered correctly if webgl.shader_validator is false.

Oh, then it's an ANGLE bug, and the fact that it renders correctly in Chromium means that it's been fixed in ANGLE and we just need to sync, but for that we are blocked on bug 578880.

We definitely need to update ANGLE before release.

This looks like fixed now. At least it's working for me. https://bugzilla.mozilla.org/show_bug.cgi?id=616290

Yep, our ANGLE copy was recently updated. Following comment 8, marking as fixed.