sway
sway copied to clipboard
swaywm
Firefox scaling isn't adjusted when moving tiled window
With a setup with two side-by-side outputs, one with a 1.75 scaling and one with a 1 scaling:
- Open Firefox tiled on the 1.75 output
- Move the workspace to the other output
- Firefox still submits buffers with a >1 scale
Goes away with WLR_SCENE_DISABLE_VISIBILITY=1.
Seems to be a firefox bug by the way of kennylevinsen's analysis. I wonder if it's possible to contribute to firefox...
can this be moved to 1.11 and sway 1.10 get released? i need explicit sync
this is not related to sway please release 1.10 i need explicit sync, i really do, i have nvidia gpu
If you want it early you can test 1.10 rc1. 1.10 will be ready when it's ready.
Please don't spam multiple issues, @SteavenGamerYT. It doesn't help. Besides, 1.10 won't have support for the explicit sync protocol, that'll be for 1.11. You can pretty easily compile from source if you need it.
If you want it early you can test 1.10 rc1. 1.10 will be ready when it's ready.
not in arch repos or aur
I had scaling issues on KDE with Firefox and some other GTK3 apps. I am confident this is not a Sway issue at all.
Can somebody confirm it is working on 1.9 and not in 1.10?
I had scaling issues on KDE with Firefox and some other GTK3 apps. I am confident this is not a Sway issue at all.
Can somebody confirm it is working on 1.9 and not in 1.10?
I only recently started experiencing this issue, and only with Firefox. I haven't updated sway from 1.9 in quite a while so I assume it has something to do with firefox
I have lots of cases where windows fail to draw at correct resolution, it's like sway isn't sending updates if the client window is busy, it's especially prevalent on Windows apps under wine, or when the Window has first opened, I usually have to resize the window again to get it to work, wouldn't be surprised if this was related.
I just got this after adding:
$ swaymsg 'for_window [title="^Extension: \(Tree Style Tab\) - Close tabs\? — Mozilla Firefox$"] floating enable'
Firefox is permanently stuck like this now lol, using swayfx but not convinced it's related to that fork.
I get a feeling there's just a bunch of resize events that are being silently dropped.