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
fix(core/ios): reset additional insets if they're zero #10134
fix(core/ios): reset additional insets if they're zero #10134
Conversation
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 67ea121. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch ✅ Successfully ran 2 targetsSent with 💌 from NxCloud. |
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.
Looks good to me - nice catch 👍
@mukaschultze @rigor789 Unfortunately, this is not fixing #10092 After trying to look what causes the problem, @cjohn001 and I concluded the following patches are currently causing trouble: See https://discord.com/channels/603595811204366337/606457628729671691/1048331850315202654 @edusperoni Removing each one of these separately was fixing the problem so I suspect a conflict between the two of them. @mukaschultze About the case of |
does not solve #10092 (comment) |
@CatchABus it's possible, although rare, to get zero for controllers that had the insets already set. For example, if we have something like: <GridLayout rows="auto, *" #1>
<GridLayout row="1" *ngIf="someConditionThatChangesDuringRouteChange" #2></GridLayout>
<GridLayout row="2" #3>
<page-router-outlet><page-router-outlet>
</GridLayout>
</StackLayout> When the This is why I thought this PR might fix #10092 too because it's a very similar issue to the one I'm facing. I've tested removing the |
Thank you very much for clarification! Hopefully, this may solve issues like #10067 |
PR Checklist
What is the current behavior?
Sometimes
additionalSafeAreaInsets
are correctly set in a layout pass but should be reset back to zero if the size if a sibling view changes. This doesn't happen and causes the safezone to be incorrectly calculated for the view that had theadditionalSafeAreaInsets
set.What is the new behavior?
additionalSafeAreaInsets
is set back to null if the newly calculated additional insets are zero.