Comment 20 for bug 1463598
Revision history for this message
| Sander van Melsen (sandervanmelsen) wrote | #20 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
Really disappointing, read #1466670 for the reason. First time some important feature for me just got killed liked that. Still feel this could have been solved more gentle, guess adjusting the reporting/filtering isn't a option?
Use WebGL a lot and this now renders Chromium complete useless, I vote for at least a flag so we can still enable it (which disables reporting of WebGL related errors?)