-
Notifications
You must be signed in to change notification settings - Fork 219
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
KeyboardSpacer does not work properly with react navigation tab bar #72
Comments
I added topSpacing={-50} and it seems to fix the issue:
|
Thanks pulpdood I will give it a shot and see how it works.
…On Mon, Jun 18, 2018 at 6:26 AM, pulpdood ***@***.***> wrote:
I added topSpacing={-50} and it seems to fix the issue:
<KeyboardSpacer topSpacing={-50}/>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#72 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQxEqqWt6Um_sXVxzr2gozztJDFUdwekks5t94BkgaJpZM4Um6o9>
.
|
I experienced the issue while applying into an 'absolute' or 'fixed' view. I could be caused by any issue, though I found out that while using 'absolute' or 'fixed' view, the calculation would be missed (similar to this described issue). I came up with a different method that supports 'absolute', 'fixed' view and publish it on react-native-spacer. |
@pulpdood while this works on some devices, it does not seem to work on all. For example I still get bars on Pixel XL 2 and iPhone X when adding |
Yet another solution:
|
thanks for direction @ESA2012. For the case of iPhoneX + tab bar. I use:
It looks like it is exact this value needed My config:
|
I'm using this for iPhone only (don't have issues on Android), and this combo solved all my problems...
|
When using the keyboard spacer it will push the textinput up an additional amount (additional amount = height of the tab bar) for both ios and android.
Works great if you aren't using a tab bar.... but most cases the developer likes to use the tab bars.
The text was updated successfully, but these errors were encountered: