-
Notifications
You must be signed in to change notification settings - Fork 3k
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
[Wayland] quick vertical resizing reverts the window dimensions to before the resize. #15610
Comments
My semi-blind guess (haven't looked at the log myself) is that there might be some race in mpv between one part of the code committing a new video frame with the previous size, another part of the code trying to change the size, and ack_configure being delivered incorrectly. I.e. if mpv sends ack_configure right away instead of together with the corresponding surface commit, this kind of issue can happen.
This is compositor-specific logic that tries to keep the opposite window edge in place during resizing; minor differences in handling can result in this. But generally if the client is well behaved everything should work without unexpected movement. |
This doesn't happen if you use |
This happens too with |
Ah maybe I just didn't try hard enough. But it doesn't happen with |
No it also happens with |
I thought I was reproducing the issue in sway but perhaps I was seeing something else? I guess I'll try niri later. |
mpv Information
Other Information
Reproduction Steps
mpv --no-config somevideo.mp4
Expected Behavior
mpv keeps the dimensions after the resize regardless of how fast I resize.
Actual Behavior
mpv reverts to its initial dimensions after the compositor already showed mpv at the requested resized dimensions.
(On Niri the video also jumps position but on KDE it does not. Maybe @YaLTeR knows why)
niri-mpv-interactive-resize-nyn-jumping.mp4
I can attach a kde recording too if requested.
Log File
output.txt
Sample Files
wayland-resize-sample.zip
I carefully read all instruction and confirm that I did the following:
--log-file=output.txt
.The text was updated successfully, but these errors were encountered: