-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Got some issue when I put the tabview in <ScrollView>. #1037
Comments
Couldn't find version numbers for the following packages in the issue:
Can you update the issue to include version numbers for those packages? The version numbers must match the format 1.2.3. The versions mentioned in the issue for the following packages differ from the latest versions on npm:
Can you verify that the issue still exists after upgrading to the latest versions of these packages? |
@changyu2hao did you just copy and paste my comment on your first issue? lol. I'm still trying to figure this out, have you made any progress? |
guys, you can set in component in _renderScene props
and hide inside tab content if this tab not active
|
@kevinmcalear No, I haven't. I gave up and use another way to do my project. But the method mentioned by @GeorgeTsendra works |
Awesome! This works great. Thank you @GeorgeTsendra (& @changyu2hao for making the issue) I modified this to be used with react hooks: to manage the required state for the tabs:
to render the tabs themselves:
what the
|
Not the best way |
@vobear do you know of a better solution I can try? |
Closing as a duplicate of #1349 |
The tab will not automatically change height while changing tabs, thus making some blank space in short tabs
Here are the versions I'm using:
"react-native-tab-view": "^2.14.4"
"react-native-gesture-handler": "^1.5.0"
"react-native-reanimated": "^1.4.0"
After further investigation, this issue is happening because I have 3 tabs, one of them much longer than the other two. All three tabs are the same height so the two shorter tabs with less content still scroll the full height of the longest tab's content. Any way to stop this?
EDIT: It looks like this library isn't designed to be used like this: #1019
The UI we have requires things to be scrollable before getting to this tab section in the app. Any suggestions on how to do something like this would be very helpful. pray
The text was updated successfully, but these errors were encountered: