Adjusting separatorLeadingInset calculation in TableViewCell #1167
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.
Platforms Impacted
Description of changes
An update to #1093
In the previous PR, it was discovered that since the Divider was added to the cell's contentView, we needed to accommodate for the additional safeAreaInset. This means that while it is no longer needed for the
.inset
Separator Type, we need to include it for the.full
type instead.Verification
Pull request checklist
This PR has considered:
Microsoft Reviewers: Open in CodeFlow