Repository navigation
macOS: backport public window blur to 0.30.x - #4832
Open
zoujiaqing wants to merge 2 commits into
Open
zoujiaqing wants to merge 2 commits into
zoujiaqing wants to merge 2 commits into
Conversation
This branch has not been deployed
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.
Summary
Backport the macOS window-blur fix from #4541 and 97fb66b to
v0.30.x. The default 0.30.13 build references private WindowServer symbols even if the application never enables blur. This can cause Mac App Store rejection under guideline 2.5.1.The default uses a public
NSVisualEffectViewbehind the rendering view. The existing raw window handle continues to point at that rendering view when blur is toggled. Theprivate-apple-apisfeature retains the previous fixed-radius blur for applications that explicitly opt in. This backport does not add the 0.31 material-selection API.Verification
cargo teston arm64 macOS: 37 passed, 4 doctests ignored.nm -ushows neither CGS import by default; the legacy feature build imports both.