Open
Conversation
Contributor
Author
eef0614 to
d7d92fa
Compare
Collaborator
79843ad to
d7d92fa
Compare
…unintended horizontal paddings
…intended vertical paddings
d7d92fa to
398a7cd
Compare
Contributor
Author
It seems like the ZStack content does not respect the container size. I will take a look later |
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.




The original code used padding to simulate spacing, which caused 3 main issues:
You can notice all of these issues in the following example image
Before this PR (With spacing of
4)After this PR (With spacing of
8)This PR addresses the problem by applying the correct spacing, ensuring that the spacing is separate from the padding:

Additionally, I updated the default spacing from
4to8to better align with the original design intent.