Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

wayland: Remove the hack to unset limits before entering fullscreen#14039

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Draft
Kontrabant wants to merge1 commit intolibsdl-org:main
base:main
Choose a base branch
Loading
fromKontrabant:wayland_libdecor_order

Conversation

@Kontrabant
Copy link
Contributor

The associated surface commit causes a warning (previously a crash) on GNOME + libdecor when clients enter fullscreen before the initial buffer commit.

This was only ever needed on GNOME, and is fixed in GNOME 49, but is waiting on upstream backports:https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4681 andhttps://gitlab.gnome.org/GNOME/mutter/-/merge_requests/4680

Fixes#14032

@KontrabantKontrabant added this to the3.x milestoneSep 24, 2025
@KontrabantKontrabantforce-pushed thewayland_libdecor_order branch 2 times, most recently frome1df180 to940d919CompareSeptember 24, 2025 18:44
@slouken
Copy link
Collaborator

Should this go in for 3.4?

@Kontrabant
Copy link
ContributorAuthor

It can't go in before the backported GNOME fixes are merged, or things will break for users on older versions.

slouken reacted with thumbs up emoji

@Kontrabant
Copy link
ContributorAuthor

Just to note, the upstream changes are merged, and should ship in 48.7 later in November.

@KontrabantKontrabantforce-pushed thewayland_libdecor_order branch 2 times, most recently from3f84db6 to683041dCompareNovember 19, 2025 16:55
@KontrabantKontrabant modified the milestones:3.x,3.6.0Dec 2, 2025
@Kontrabant
Copy link
ContributorAuthor

Tagging this to go in early in the 3.6 cycle. The changes are upstream in GNOME, but they still need time to propagate and be backported where required, and I have some other windowing work that stacked nicely on top of this, regarding how windows with a min/max size and aspect are handled when the compositor demands that the window be a certain size, such as with maximized or tiled windows.

Wayland is sometimes at-odds with clients that want to enforce an aspect ratio or min/max window size, as certain window states have dimensions that either must be obeyed (maximized), or will give terrible results if they aren't (tiled). Use viewports and/or a masking subsurface to handle cases where surfaces are unable to match the exact window size.The masking system also allows for switching the emulated fullscreen modes to aspect-correct by default, as it will handle masking non-native aspect ratios on compositors that don't automatically mask around fullscreen windows.
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

3.6.0

Development

Successfully merging this pull request may close these issues.

wayland: Full screen ioquake3 window reports size to compositor as 0x0 pixels

2 participants

@Kontrabant@slouken

[8]ページ先頭

©2009-2025 Movatter.jp