Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WebGL no longer works in Firefox 83 #549

Closed
5 of 6 tasks
DaMatrix opened this issue Nov 19, 2020 · 7 comments
Closed
5 of 6 tasks

WebGL no longer works in Firefox 83 #549

DaMatrix opened this issue Nov 19, 2020 · 7 comments
Labels
bug Something is not working properly

Comments

@DaMatrix
Copy link

DaMatrix commented Nov 19, 2020

Checklist (issue will be disregarded & closed if incomplete!)

  • I've checked both open and recently closed issues to ensure this issue is not already reported.
  • I am using the newest version of TETR.IO.
  • I know how to reproduce the issue.
  • I am using a supported browser or the Desktop Client.
  • I am not using anything that modifies game code (e.g. TETR.IO+).
  • I am certain this is a bug, not a feature request.

Describe the bug/issue

Just upgraded Firefox to version 83.0, and tetr.io no longer works. I don't know whether or not Firefox is even supported (it's mentioned in the issue template that I should be using a "supported browser", but I couldn't find a list of "supported browsers", only something that recommends that I use something Chromium-based). Anyway, I now get the following message when trying to load the game:

TETR.IO requires WEBGL

it seems WEBGL is disabled in your browser. WEBGL is required for the game to render properly.

please check your browser settings to ensure WEBGL is enabled in your browser, then try again.

this often happens if HARDWARE ACCELERATION is turned off in your browser. try enabling it in browser settings.

if nothing works, try upgrading your browser

It worked fine before updating, and I know WebGL is working correctly (I tried a number of WebGL tests/benchmarks and all of them ran flawlessly).

Reproducing

Install Firefox 83.0 and try to use tetr.io...

Expected behavior

That it'd work

Screenshots

error message

Your setup

  • OS and version: kubuntu 20.04
  • Browser and version: Firefox 83.0+build2-0ubuntu0.20.04.1

Additional context

@DaMatrix DaMatrix added the bug Something is not working properly label Nov 19, 2020
@Tisawesomeness
Copy link

I can also confirm this bug, since tetr.io was working before Firefox updated and broke after the update. Currently on the same firefox version, ubuntu 20.04. It works on Chromium 87.0.4280.66, so the issue seems to be specific to Firefox. Can anyone on Windows test this?

@UniQMG522
Copy link

Not seeing any issue on W10 on Firefox 84.0b2 (beta channel)

@ziggystar
Copy link

ziggystar commented Nov 20, 2020

I've tracked it down to the following problem:

  • In Firefox under linux, hardware-compositing (hw_compositing) is disabled (by platform). This can be checked under about:support
  • It can be forced under about:config using layers.acceleration.force-enabled and restarting firefox. Then tetr.io works as expected

The big question for me is, why did the check start failing? Was it a change in Firefox, or was it a change in tetr.io. Also apparently tetr.io has been running fine for me before forcing the compositor to be enabled. Is this check needed at all? Does it come from some library?

@Tisawesomeness
Copy link

In the console I have
Failed to create WebGL context: failIfMajorPerformanceCaveat: Compositor is not hardware-accelerated.
The debugger shows pixi.js threw the error, and since the page source says pixi was compiled in April, I doubt it's a change in tetr.io. We'll need to take up the issue with Firefox.

@DaMatrix
Copy link
Author

DaMatrix commented Nov 20, 2020

  • It can be forced under about:config using layers.acceleration.force-enabled and restarting firefox. Then tetr.io works as expected

thank you for this! i figured there would be a temporary workaround like this, but had no idea where to look. hopefully an official fix arrives soon.

@roynico
Copy link

roynico commented Dec 8, 2020

I confirm the issue. I also get the error message since I updated to FF 83.0 (64-bit)

@o5k
Copy link
Member

o5k commented Dec 8, 2020

This seems to be due to a change through https://bugzilla.mozilla.org/show_bug.cgi?id=1679671 - I have found a bypass though which will go in effect next patch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something is not working properly
Projects
None yet
Development

No branches or pull requests

6 participants