[Wayland] HiDPI scaled displays are not detected, firefox needs restart
Categories
(Core :: Widget: Gtk, defect, P3)
Tracking
()
People
(Reporter: jhnmlkvch9, Unassigned)
References
(Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:77.0) Gecko/20100101 Firefox/77.0
Steps to reproduce:
Open Firefox-nightly on a HiDPI display which is set to a scaling factor 1.5.
This is build 77.0a1 (2020-04-07) on Wayland with GDK_BACKEND=wayland
Actual results:
The menus are huge and not scaled correctly
Expected results:
The menus should scale just like the rest of the interface.
Comment 1•5 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
Comment 2•5 years ago
|
||
This is a problem with experimental partial scaling. The menus are correct when scale 1x or 2x is used, correct?
Reporter | ||
Comment 3•5 years ago
|
||
This is weird. The huge hamburger menu that I was seeing with 1.5 scaling in yesterday's nightly has been fixed today. Is this an intentional change that fixed this? 2x scaling sort of works in the sense that the menu is scaled correctly, but it does not make use of the entire real estate of the screen. Instead it comes down about 2/3rds of the page and puts a scroll bar on the menu. To re-iterate this is only the hamburger menu, regular menu items are working fine.
Comment 4•5 years ago
|
||
Can you please attach a screen of the broken firefox with 2x scale? I use that every day on my own box and I don't see any issue here. The 1.5 scaling is managed by wayland compositor, it's not handled by Firefox itself, Firefox handles only non-partial scales.
Also which distro/DE do you run?
Thanks.
Reporter | ||
Comment 5•5 years ago
|
||
I figured out the cause of the problem. The scaling of menus, popup windows etc. in Firefox gets messed up if I hot plugin an external monitor with a non default scaling after Firefox has already been running. Once the external monitor with 2 or 1.5 scaling is plugged in, in order to get the scaling of these elements right, I need to restart Firefox. Once restarted everything is fine again.
I'm using Sway on Archlinux. Let me know if this is a Sway issue, I'll report it there.
Updated•5 years ago
|
Comment 6•5 years ago
|
||
Because this bug's Severity has not been changed from the default since it was filed, and it's Priority is P3
(Backlog,) indicating it has been triaged, the bug's Severity is being updated to S3
(normal.)
Comment 7•4 years ago
|
||
I think it's a sway issue when wl_output is not updated. Can you please try mutter/gnome if you can reproduce it?
Thanks.
Description
•