Elements in Firefox UI and on webpages appear boxy on Firefox for ARM (Windows)
Heyo,
A bit of a weird bug..
Some elements of Firefox's UI, and even elements on webpages that are supposed to be boxes with rounded corners (or squircles) appear with straight rectangular edges.
Furthermore, when hovering over content sometimes, the shading seems to be quite off.
I've attached a couple screenshots to elaborate on this..
Alle Antworten (11)
Does this help:
- /questions/1425975 Round corners disabled
You can also try other gfx.webrender prefs as a test:
- gfx.webrender.software = true
- gfx.webrender.use-optimized-shaders = false
cor-el said
Does this help:
- /questions/1425975 Round corners disabled
Hey,
Thanks for your reply!!
Changing gfx.webrender.debug.disable-batching to true in about:config did not fix the issue, and further, made all webpages jumble up lol (see debug4.png attachment).
However, starting in Troubleshoot mode did fix the issue.
After restarting back into Normal mode, disabling my Addons didn't fix it, but disabling Hardware Acceleration did - so I believe there must be some sort of incompatibility with the Microsoft/Qualcomm SQ chip despite these being the only chips on Windows on ARM devices produced at the moment.
I wouldn't want to use a browser with hardware acceleration completely turned off, so I turned it back on.
In saying this, changing gfx.webrender.software to true also fixed the issue. Is this equivalent to turning hardware acceleration off in Firefox settings, and will I experience any performance drawbacks because of this?
Appreciate your help :)
Please run mozregression between versions 113 and 116 to find when this first started so it can be fixed.
zeroknight said
Please run mozregression between versions 113 and 116 to find when this first started so it can be fixed.
Done! Please see the attached screengrab for the details.
That narrows it down to between 2023-05-13 and 2023-05-23 but that's still a lot changes. It should be possible to go further to the specific day and even build. Is there any reason why you stopped at 2023-05-18?
zeroknight said
That narrows it down to between 2023-05-13 and 2023-05-23 but that's still a lot changes. It should be possible to go further to the specific day and even build. Is there any reason why you stopped at 2023-05-18?
I misunderstood the mozregression process lol.
Now done! Please see the attached screengrab.
I've saved the mozregression log to a .txt file in case there's anything useful in there. Can be found here: mozregression Log File
Did you test with "gfx.webrender.software = false " and "gfx.webrender.use-optimized-shaders = false "?
Nice work. From that it appears Bug 1852440 is already tracking this issue but devs have been unable to reproduce it.
TyDraniu said
Did you test with "gfx.webrender.software = false " and "gfx.webrender.use-optimized-shaders = false "?
Hey,
Changing gfx.webrender.software to true fixes the issue.
Is this equivalent to turning hardware acceleration off in Firefox settings, and will I experience any performance drawbacks because of this?
zeroknight said
Nice work. From that it appears Bug 1852440 is already tracking this issue but devs have been unable to reproduce it.
That's the exact same issue but with a slightly different machine to mine (theirs is a Gen1 Surface Pro X, and mine is a Gen2 model)!
I added a comment to the case linking back to this conversation thread.
I think the devs haven't been able to reproduce the issue cuz they're trying with a Lenovo machine, and different Windows on ARM laptops.
For some reason, I believe this issue persists only for users of Surface Pro X and Surface Pro 9 5G laptops.