Here’s what Leago said about the webgl errors:
I’ve made the fallback check more broad. Will be in the next deploy, on Monday
May also be helpful to verify if their bug is indeed webGL related by having them try these test urls:
The Get WebGL is he one I already used to see WebGL1 works fine.
I thought that since the browser knows WebGL2 is not working that would be good enough for fallback coding.
As far as I can tell the video driver I have from Lenovo is actually newer than the generic Intel one for the processor.
I will try on some other machines and Linux tomorrow.
I’ve forwarded your message to Leago.
Same results on other non WebGL2 machines win10 & Linux.
It is working! At least no issue to first page.
Based on yesterday’s tag-up call, it sounds like they tighted up the webgl detection issues so much that the floating chess pieces have pretty much disappeared. Personally, I’d be OK with that, as would a number of people on the Forums, but I suspect Leago will try to loosen the rules up so that they appear on systems capable of supporting WEBGL2, hopefully without breaking it for others again.
As far as I can tell, WEBGL2 is not currently being used anywhere else, but there may be places it is used that I haven’t run across yet or there may be plans to use it down the road.