gfx.webrender.compositor.force-enabled freezes windows in fullscreen and maximized state
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
People
(Reporter: sebastian, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
|
36.97 KB,
application/json
|
Details |
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:90.0) Gecko/20100101 Firefox/90.0
Steps to reproduce:
Firefox 90.0b1 mozilla-flatpak-1.0
GNOME Shell 40.1 wayland mode
Does not happen on X11. This is a regression and worked in a previous version of firefox (I don't know which version though).
new profile, set all to true:
- gfx.webrender.all
- gfx.webrender.enabled
- gfx.webrender.compositor.force-enabled
Maximize or fullscreen a window.
Actual results:
The surface freezes until it is put back into windowed mode (input is still received).
Expected results:
The surface should not freeze.
|
||
Updated•3 years ago
|
|
|
||
Comment 1•3 years ago
|
||
I assume the only reason this didn't occur in previous versions was because there was no compositor to enable. Likewise why it doesn't occur on X11.
|
|
||
Comment 2•3 years ago
|
||
Senastian, thank you for the bug report. Could you please attach a copy of your about support information to the bug.
Could you also confirm whether disabling gfx.webrender.compositor.force-enabled fixes the issue. ie With webrender enabled, but the compositor disabled.
I assume the only reason this didn't occur in previous versions was because there was no compositor to enable. Likewise why it doesn't occur on X11.
Maybe but what I don't understand then is why on my main profile it got enabled suddenly without me changing anything.
Could you also confirm whether disabling gfx.webrender.compositor.force-enabled fixes the issue. ie With webrender enabled, but the compositor disabled.
Yes, the bug is fixed with webrender enabled and the compositor disabled.
Also bug 1699754 says that the compositor should work on GNOME Shell 40.1.
|
|
||
Comment 5•3 years ago
|
||
Thanks for the information.
Maybe but what I don't understand then is why on my main profile it got enabled suddenly without me changing anything.
Had you previously set gfx.webrender.compositor.force-enabled to true, or did that happen by itself? If you set it to true yourself, then until recently it won't have done anything as there wasn't a compositor on wayland to enable (the pref only had an effect on Windows and Mac). Recently the in-development wayland compositor was added, so the pref started to have an effect.
Also bug 1699754 says that the compositor should work on GNOME Shell 40.1.
Yes, but it's very new code (both on the Firefox and gnome/wayland sides) so there are likely to be bugs. I'll wait for Robert to comment as he is more likely to understand what the issue is.
Had you previously set gfx.webrender.compositor.force-enabled to true, or did that happen by itself? If you set it to true yourself, then until recently it won't have done anything as there wasn't a compositor on wayland to enable (the pref only had an effect on Windows and Mac). Recently the in-development wayland compositor was added, so the pref started to have an effect.
Ah, I think I had. That explains that mystery. Thanks.
|
||
Comment 7•3 years ago
|
||
(In reply to sebastian from comment #6)
Had you previously set gfx.webrender.compositor.force-enabled to true, or did that happen by itself? If you set it to true yourself, then until recently it won't have done anything as there wasn't a compositor on wayland to enable (the pref only had an effect on Windows and Mac). Recently the in-development wayland compositor was added, so the pref started to have an effect.
Ah, I think I had. That explains that mystery. Thanks.
Exactly :)
This will be fixed by bug 1711244
Description
•