You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current logic in SamplesContainerNode means there's always a 40.dp top padding – even on elements without a back button, and even on the samples list itself.
The padding should only be applied to the child which corresponds to the NavTarget with showBackButton == true.
The text was updated successfully, but these errors were encountered:
If you have different padding values the screen transitions don't look great. if you come up with a solution for that, please keep that in mind when switching between screens.
I think I know what you mean – there's a visual "jump" if we change the padding value. But if we only apply the padding on the needed element rather than the container, this shouldn't happen, no?
The current logic in
SamplesContainerNode
means there's always a40.dp
top padding – even on elements without a back button, and even on the samples list itself.The padding should only be applied to the child which corresponds to the
NavTarget
withshowBackButton == true
.The text was updated successfully, but these errors were encountered: