Repository navigation
SnackBars show behind the keyboard #143
Description
Activity
Comment by j9brown
Tuesday Aug 25, 2015 at 21:06 GMT
FWIW, Android won't tell you whether the keyboard is visible.
So in general the application is left with deciding how it wants to deal
with incursions into its space by an IME or other parts of the system UI
based on other information provided during layout, particularly the content
insets.The Android window manager provides the application with content inserts
which represent what part of the window will be visible. The app may be
able to draw outside of that region but what it draws there may or may not
be visible since it might be covered by decorations like the status bar but
that's how translucent decorations work. Typically the app will adjust its
content view's layout to fit that region (the framework can do this
automatically).If you've got a snack bar, you'll want to anchor it to the bottom of the
content region of the window.It may help to think of the app's layout as having both an outer decor part
(which contains the background and decor elements like the title bar which
fill the window) and an inner content part (which fits within the decor and
adjusts as the content region changes).NB. I might be getting the details slightly wrong. There are also
affordances for things like overscan regions but I think most of that is
hidden from the API.See also:
https://developer.android.com/reference/android/view/View.html#setFitsSystemWindows(boolean)On Tue, Aug 25, 2015 at 1:39 PM Eric Seidel [email protected]
wrote:Not sure if they're supposed to sit above the keyboard or what? Or maybe
we're supposed to use a different widget when the keyboard is visible?I discovered this by entering an invalid number in the fitness app.
—
Reply to this email directly or view it on GitHub
https://github.com/domokit/sky_engine/issues/810.- added a commit that references this issue
on Mar 21, 2019 this worked for me : remove this line : resizeToAvoidBottomInset:false
from ScaffoldThis thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.- locked as resolved and limited conversation to collaborators
on Aug 3, 2021
Tuesday Aug 25, 2015 at 20:39 GMT
Originally opened as https://github.com/flutter/engine/issues/810
Not sure if they're supposed to sit above the keyboard or what? Or maybe we're supposed to use a different widget when the keyboard is visible?
I discovered this by entering an invalid number in the fitness app.