Blurry layout and text with fractional scaling
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: fabricio, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:106.0) Gecko/20100101 Firefox/106.0
Steps to reproduce:
Using Arch Linux and KDE Wayland I updated from firefox-developer-edition 106.0b6-1 to 106.0b7-1.
Actual results:
Even though fractional scaling was not 100% perfect before, it was bearable.
When I updated it got way blurrier, similar to an application using xwayland.
Expected results:
The layout and text should've stayed the same as it was before the update.
(If I rollback to b6 it goes back to normal)
It may be something wayland related because touchpad gestures (zoom, swipe to go back/foward) are not working either for me on ff >= 106b7
|
||
Comment 2•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
|
||
Comment 3•2 years ago
|
||
If you're willing to use mozregression to find a regression range that will likely be helpful. You can plug in the regression range you already know to make it go faster.
Sure, here is the output:
2:32.40 INFO: Narrowed integration regression window from [bf74bc66, 3f068e96] (3 builds) to [bf74bc66, 5126dcd0] (2 builds) (~1 steps left)
2:32.40 INFO: No more integration revisions, bisection finished.
2:32.40 INFO: Last good revision: bf74bc664e5a0f3161482a632695d6b5bf9fa295
2:32.40 INFO: First bad revision: 5126dcd045c8cb2d7bf5cc1841d970e15a1ac9bd
2:32.40 INFO: Pushlog:
https://hg.mozilla.org/releases/mozilla-beta/pushloghtml?fromchange=bf74bc664e5a0f3161482a632695d6b5bf9fa295&tochange=5126dcd045c8cb2d7bf5cc1841d970e15a1ac9bd
I've updated to firefox-developer-edition 107.0b1-1 and the issue seems to be fixed
|
||
Comment 6•2 years ago
•
|
||
Reporter, that pushlog indicates that EARLY_BETA_OR_EARLIER was reset. This is a build flag that gets used to enable experimental features. In preparation for the final release of Firefox, this flag is reset after the 6th beta (roughly the last two weeks of a beta cycle) to allow users to test something that is closer to what the stable population will receive.
My pet theory is that because Firefox's Wayland backend is only enabled by default when EARLY_BETA_OR_EARLIER is true, you ended up getting punted to XWayland when it was false. Now that we've entered a new beta cycle and EARLY_BETA_OR_EARLIER is true, you are once again using the native Wayland backend.
We can confirm this theory if you manually disable Firefox's Wayland backend by launching it with MOZ_ENABLE_WAYLAND=0.
Changing MOZ_ENABLE_WAYLAND to 0 on the current beta (107.0b1) shows the same behavior as 106.0b7-106.0b9. So it seems that your theory is correct.
To double check I've tried it the other way: downgraded to 106.0b7 and launched it with MOZ_ENABLE_WAYLAND=1 and it works.
So until Wayland is enabled by default in the stable release, I'm setting that env variable in /etc/environment.
|
|
||
Comment 8•2 years ago
|
||
Great to hear!
Description
•