-
Notifications
You must be signed in to change notification settings - Fork 645
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
Wrong content scrolling with scrollview child #265
Comments
Hi, have you fixed this? thanks. |
Nope, still waiting for an answer to this issue... I fear I will have to find an alternative to RNKASV... :/ |
Hi @lightman73 Have you tried to test this in a real device? |
Hello, yes, tried it on an iPhone 6s with iOS 11.2.6, and iPhone 7 with iOS 11.0.3, same behaviour... |
Thanks @lightman73 We're in the middle of a super important release, I promise I'll check this out next Tuesday. We're super limited on resources right now. Also, any other hint or even a PR will be highly appreciated. |
Thanks ! If I get some other insight on the issue I'll let you know :) |
Hi, I just tried 0.7.0, and it's still showing the same behaviour. Did you find the time to have a look at the issue ? Thanks again ! |
One question @lightman73, why the extra |
have same problem ;( Is there any news? |
Facing the same problem. Any updates, @alvaromb? |
Facing same problem, Problem occur in TabNavigator |
Facing the exact same problem too. |
For all of you facing this issue: |
What @Nirony said is a good lead. But if you still need 2 scrollView, I think that the behaviour you are seeing @lightman73 is that the 2 scrollView are pushing the content to the top for the keyboard space, and one is too much. |
Any updates on this issue? I am facing the same. |
Hello, I've got a problem with an app I'm developing for a client.
The structure of the page is like this:
As long as the focused TextInput is at the top of the ScrollView, everything's fine, but as you focus on TextInputs further down the ScrollView, RNKASV scrolls the content up way too much, to the point of having the focused TextInput outside view, as you can see in the attached screenshots.
Please note that I'm using react-native-navigation, and the page is inside a TabNavigator, inside a StackNavigator, inside a TabNavigator (don't ask, please; I already tried to explain the client that having a status bar, and two tabbars on the same page will be confusing for the user, but they're not listening...) (the StackNavigator contains only the inner TabNavigator, and it's there only to have the status bar at the top).
I'm using :
Any help will be greatly appreciated...
Thanks !
The text was updated successfully, but these errors were encountered: