-
Notifications
You must be signed in to change notification settings - Fork 0
[playground] verify animations on layer and view boxes side by side #7
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
Open
honghaoz
wants to merge
3
commits into
master
Choose a base branch
from
playground-update
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
🔎 Supported by static analysis
🏁 Script executed:
Repository: honghaoz/ComposeUI
Length of output: 12749
🏁 Script executed:
Repository: honghaoz/ComposeUI
Length of output: 9896
🏁 Script executed:
Repository: honghaoz/ComposeUI
Length of output: 18063
🏁 Script executed:
Repository: honghaoz/ComposeUI
Length of output: 8228
🏁 Script executed:
Repository: honghaoz/ComposeUI
Length of output: 50375
🏁 Script executed:
Repository: honghaoz/ComposeUI
Length of output: 50376
🏁 Script executed:
Repository: honghaoz/ComposeUI
Length of output: 23403
🏁 Script executed:
Repository: honghaoz/ComposeUI
Length of output: 1197
🌐 Web query:
Apple UIKit traitCollectionDidChange displayScale documentation CATextLayer contentsScale automatic update💡 Result:
In UIKit, the
contentsScaleproperty of aCATextLayerdoes not update automatically when thedisplayScaletrait changes [1][2]. WhileUIViewautomatically manages thecontentsScaleof its primary backing layer, customCALayerobjects—includingCATextLayerinstances you create and manage yourself—require you to update this property manually to match the current screen or trait resolution [1][2]. To handle these updates, you should monitor trait changes and explicitly set thecontentsScaleon yourCATextLayer[1][2]. Modern best practices involve using trait registration rather than overriding the deprecatedtraitCollectionDidChange(_:)method [3]. Recommended approach: 1. Register forUITraitDisplayScalechanges: Use theregisterForTraitChanges(_:handler:)method (available onUITraitChangeObservabletypes) to observe changes to the display scale [4][3]. 2. Update the layer: In the registration handler, update thecontentsScaleproperty of yourCATextLayerto reflect the newdisplayScalefrom the trait collection [4][1]. 3. Alternative (visionOS): If you are targeting visionOS, consider using thewantsDynamicContentScalingproperty on yourCATextLayer. When set totrue, this property allows the system to automatically handle resolution scaling for vector-based content like text [5]. For platforms other than visionOS, or whenwantsDynamicContentScalingis not used, manually settinglayer.contentsScale = traitCollection.displayScale(orUIScreen.main.scale) is the required standard to ensure text remains crisp [1][6][2].Citations:
Refresh labels when the display scale changes.
On UIKit,
BaseScrollView.traitCollectionDidChange(_:)only schedules a theme update. If onlydisplayScalechanges, the theme remains unchanged, so no Compose refresh updates theCATextLayerinstances. They can retain the oldcontentsScale. Handle the display-scale change or add a regression test.🤖 Prompt for AI Agents