-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
floating mpv window flickers and changes position when resizing #7501
Comments
Resizing a floating mpv horizontally, the height seems to briefly jump to what it's supposed to be:
Could be related to #5266. However, it doesn't look like mpv uses set_window_geometry. |
The same problem is mentioned in #7195 (comment). sway ends up setting the size in two different places:
|
Seems to be a wlroots issue. since it also affects riverwm |
No, it's a sway/river issue and it's fixed on river already but the fix is unreleased riverwm/river@9db4111 |
I will check if i have the patch put on opensuse factory. 🤔 |
tested it. it's neither a wlroots issue nor a wayland issue (it can be) since it also happens in GNOME or KDE Plasma Wayland |
It doesn't happen in river patched with that commit, or on Weston (according to upstream issue), or on KDE/Gnome. Are you sure you're experiencing the same issue? |
Nvm it was another issue. It's this one mpv-player/mpv#11420. i read this issue wrong |
Partially fixed by #8295 and the corresponding wlroots change, now the SSD (borders) is always correct at least. The window however still flickers while you're resizing and can change position. |
sway git
Video: https://0x0.st/HiBi.mp4
How to reproduce: start mpv with
--no-config
as a floating window, and try to resize to 0x0 or like in the videoOriginal issue here mpv-player/mpv#11435
The mpv window does nothing besides try to keep the aspect ratio when resizing, I don't know of any other client that wants to do that so I can't say if it's just mpv or any application that wants to keep a certain aspect ratio...
wayland_debug.log
The text was updated successfully, but these errors were encountered: