After yesterday's update, when I go full screen on my Facebook game, the screen gets a grayish tint to it.
Categories
(Firefox for Android :: General, defect)
Tracking
()
People
(Reporter: jennie522, Unassigned)
Details
Attachments
(1 file)
|
2.16 MB,
image/png
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:139.0) Gecko/20100101 Firefox/139.0
Steps to reproduce:
Yesterday, Firefox updated.
I opened June's Journey through Facebook like I do every day & went into the full screen mode.
Actual results:
The screen changed from clear color to a grayish appearance.
Expected results:
The picture should have stayed clear color without the film effect over the top.
Comment 1•8 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Firefox for Android::General' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
| Reporter | ||
Comment 2•8 months ago
|
||
In my case, not Android.
I am using Windows 11 on an HP Laptop.
I have seen others report the problem as a blue screen which appears in full screen mode on Facebook games.
Comment 3•7 months ago
|
||
I can confirm that this happens for me with Facebook Games, whenever I switch to full screen mode. This seems to be related to Unity WebGL canvas builds, as mentioned in this thread in the Unity Forum: https://discussions.unity.com/t/odd-issue-with-focus-in-firefox/1651226/2
Comment 4•7 months ago
|
||
(In reply to Ru Cindrea from comment #3)
I can confirm that this happens for me with Facebook Games, whenever I switch to full screen mode. This seems to be related to Unity WebGL canvas builds, as mentioned in this thread in the Unity Forum: https://discussions.unity.com/t/odd-issue-with-focus-in-firefox/1651226/2
According to the Unity Forum thread:
"Firefox wants to consider the canvas as selectable and as it goes into fullscreen. Firefox is erroneously thinking it should select the canvas element when you click on it."
I can also confirm that this only happens with the 139 version of Firefox, earlier versions did not have this problem.
Description
•