Created attachment 1679150 [details] Firefox rendered too large after reducing scaling Description of problem: I have my internal screen set to 125% scaling. When I plug an external screen for which I set scaling to 100%, overall scaling is reset to 100%. Whenever the scaling is changed by that means, Firefox's layout doesn't seem to follow. The window borders in Gnome's overwiew are correct, also mouse clicks seem to be caught correctly – but visually you only see part of the scaled-up Firefox UI, or it only takes ⅔ of the window and the rest is black. See screenshot for a Gnome overview after setting scaling from 100% to 125% while Firefox was open. Version-Release number of selected component (if applicable): 75.0 but I've seen the issue since upgrade to F31. How reproducible: Always. Steps to Reproduce: 1. Open Firefox on Wayland. 2. Set increase screen scaling, f.e. from 100% to 125% or 200% 3. Open Gnome's overview (by pressing Super or clicking "Activities" Actual results: * Firefox' UI stays scaled, and is cut off. * Inputs seem to be accepted in the right places (clicking top right somewhere will open the menu) Expected results: Also the UI scales after scaling changes Additional info: See screenshots
Created attachment 1679151 [details] Firefox rendered too small after scaling up
Can you please try latest nightly under Wayland [1]? Thanks. [1] https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Testing_Mozilla_binaries
Hi Martin. Thanks for getting back to me. This morning I tried using two screens with different scales, and dragging the window between the two screens is showing the issue as well. I tried the latest nightly with Wayland backend, and everything's fine. Following that, I tried launching my installed Firefox with a clean profile, and it's fine as well. So it must be some profile setting that is disturbing. I remember setting some things to ensure Firefox uses hardware acceleration on my system, which might be the cause. I'll investigate.
It seems to have been the combination of - layers.acceleration.force-enabled - gfx.webrender.all that caused the issue. I changed their defaults to fix some issues which I had with WebGL. Thanks!
Apparently another upgrade fixed it, it works now even with layers.acceleration.force-enabled active.