-
Notifications
You must be signed in to change notification settings - Fork 25.2k
[iOS] Fixes scrollIndicatorInsets not work in old arch #46944
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
Closed
zhongwuzw
wants to merge
3
commits into
facebook:main
from
zhongwuzw:features/fix_scrollIndicatorInsets
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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.
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.
This is a breaking change. JS would not see the vertical scroll indicator anymore and JS components that use it will break. Can we:
verticalScrollIndicatorInsetspropscrollIndicatorInsetspropsverticalScrollIndicatorInsetsprop uses thescrollIndicatorInsetsunder the hoodThere 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.
@cipolleschi I don't see ScrollView props have
verticalScrollIndicatorInsets, actually it's changed fromscrollIndicatorInsetspropstoverticalScrollIndicatorInsetsin #44820 , but I don't know why..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.
Yeah, we need to keep the
verticalversion around, because theRCT_EXPORT_VIEW_PROPERTYmacro exposes theverticalScrollIndicatorInsetsto JS and there might be product code that uses that prop.If we change it to
scrollIndicatorInsets, the product code will break.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.
@cipolleschi I restore the
verticalScrollIndicatorInsets, but actually, if product use it, it would crash becauseRCTScrollViewnot implements verticalScrollIndicatorInsets methods.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.
How did it work before? 😱
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.
I couldn't find any relevant context in the pull request at #44820. It may just be an oversight. :)