Support transparancy in toplevel export#12824
Merged
vaxerski merged 4 commits intohyprwm:mainfrom Jan 20, 2026
Merged
Conversation
|
Hello and thank you for making a PR to Hyprland! Please check the PR Guidelines and make sure your PR follows them. If your code can be tested, please always add tests. See more here. beep boop, I'm just a bot. A real human will review your PR soon. |
vaxerski
reviewed
Jan 3, 2026
3a2c560 to
bbc6245
Compare
vaxerski
reviewed
Jan 5, 2026
1df0347 to
3abdc1d
Compare
Contributor
Author
|
Sorry change took so long to happen |
3abdc1d to
d42ff25
Compare
vaxerski
previously approved these changes
Jan 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Describe your PR, what does it fix/add?
Clears buffer with transparent pixels instead of black when copying a surface with toplevel export.
closes #11192
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
I am unsure whether tests are necessary for this pr due to it being rendering related
Is it ready for merging, or does it need work?
yes