removeClippedSubviews={true} in scrollview - view not visible when changed tab
See original GitHub issueremoveClippedSubviews={true}
in scrollview - view not visible when changed tab
When launched an app for the first time the scroll view is visible but when I change the tab i.e. perform any navigation the scroll view is not visible until it is scrolled
removeClippedSubviews={true}
using this as true
makes my scroll view perform faster the only issue is that the view gets hidden sometimes on the navigation
FYI: removeClippedSubviews={false}
doesn’t reproduce the hidden issue but degrades the performance
Any idea how to fix hidden issue while having removeClippedSubviews={true}
?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Common bugs in React Native ScrollView and how to fix them
removeClippedSubviews – A Boolean that, when enabled (it's false by default), detaches views that are outside the viewport from the native view ......
Read more >Listview does not scroll inside scrollview ... - Stack Overflow
The result am getting now is listview inside tabs are not scrolling. when I enable scroll on parent scrollview the whole layout will...
Read more >ScrollView - React Native
When true, the scroll view bounces horizontally when it reaches the end even if the content is smaller than the scroll view itself....
Read more >ScrollView · React Native 中文
When true, the scroll view stops on multiples of the scroll view's size when scrolling. This can be used for horizontal pagination. The...
Read more >react-native-tab-view - npm
When true , the scroll view bounces when it reaches the end of the content. The default value is false . Using with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
FYI, if you search the issue history, this is atleast 4 year old react-native bug.
@krunalbad thank you for the issue. Can you make sure to follow the template and provide a repro of the issue. Closing for now.