[Tabs] Correct MDCTabBarView behavior for contentInset. #8512
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.
When
contentInset
is non-zero, MDCTabBarView was misplacing the tabs views.This PR corrects the issue by making the following changes:
contentSize
to fill the entire safe areabounds.
contentSize
to fill at least the entire safearea bounds.
longer depend on the min-X position of the bounds.
layoutSubviews
to handle caseswhere scrolling adjusted the X-offset of the bounds.
Fixes #8236