forked from androidx/androidx
-
Notifications
You must be signed in to change notification settings - Fork 114
Fix consuming window insets in system window insets padding #2665
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
Merged
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
95aa530
Fix insets not consumed when using system window insets padding
svastven 270e934
Override toString for PlatformInsets.toWindowInsets
svastven cda966f
Add skiko tests for consuming WindowInsets
svastven e08b8a6
Fix InsetsConsumigModifierNodeKey value
svastven cb8a693
Move InsetsConsumingModifierNodeKey from common to skiko source set
svastven e2c0104
Fix InsetsConsumingModifierNode traverseKey
svastven 93411be
Fix equals implementation in PlatformInsetsPaddingModifierElement for…
svastven 7b3944f
Remove unused imports
svastven 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
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
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
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.
Adding both of them works, but kind of suspicious and creates more elements to allocate/iterate/etc 🤔
Just to be informed: what's about these alternatives?
PlatformWindowInsetsProviderNodefromInsetsPaddingModifierNode(not visa versa).DelegatableNode.visitAncestors(includeDelegates = true)(1) looks more promising for me. WDYT?
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.
The problem in general is that both the
PlatformWindowInsetsProviderNodeandInsetsPaddingModifierNodeare traversable (they have different TraverseKey) and need to traverse their respective descendants to update them with ancestor properties.As for
PlatformWindowInsetsProviderNodefromInsetsPaddingModifierNodebut the problem is that the commonInsetsPaddingModifierNodeis not aDelegatingNodeso we cannot delegate from it to another node. And I am not sure we want to make it aDelegatingNodein common just to use this functionality on the platform level. Also I think that the problem with the delegated node not being discovered would still remain. Or do you see some other option that I don't?DelegatableNode.visitAncestors(includeDelegates = true)is internal tocommonMainso is the idea to use it inInsetsConsumingModifierNodeinstead oftraverseAncestors?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.
It's internal to the module, not source-set