Should navbar height be removed from keyboard to footer margin? #572
vilindberg
started this conversation in
General
Replies: 1 comment
-
|
You'll have to detect keyboard on your end -- I can't do it in the library since footer is not always a button, like in your use-case. Footer's behavior is just a floating component, positioning and styling is up to you. The docs just adds tip, and honestly, might be better to remove it to avoid confusion. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
When using bottom insets (like in the docs, https://sheet.lodev09.com/guides/footer#safe-area-handling) on an Android with navigation buttons, the footer button is pinned to top of the navigation bar.
But when the keyboard is opened, the navigation bar height is added to the margin between the keyboards top and the bottom of the footer button. Should this really be the case? If yes, should it be handled be removing the insets bottom padding if the keyboard is opened?
See images:


Beta Was this translation helpful? Give feedback.
All reactions