summaryrefslogtreecommitdiffstats
path: root/docs/html/develop
diff options
context:
space:
mode:
authorJohn Spurlock <jspurlock@google.com>2013-10-18 17:34:42 -0400
committerJohn Spurlock <jspurlock@google.com>2013-10-18 18:41:22 -0400
commitae3349e1c34f7aceddc526cd11d9ac44951e97b6 (patch)
treecb239dd55da5783b75d452982c80d508d70e4edf /docs/html/develop
parentac2d61a2d731946afed300d63039d6d712fd7f4c (diff)
downloadframeworks_base-ae3349e1c34f7aceddc526cd11d9ac44951e97b6.zip
frameworks_base-ae3349e1c34f7aceddc526cd11d9ac44951e97b6.tar.gz
frameworks_base-ae3349e1c34f7aceddc526cd11d9ac44951e97b6.tar.bz2
Move the IME navigation guard view up to decor.
Although the IME windows are now allowed to extend into the nav bar, some IMEs were making assumptions about computed insets based on the height of the content view. So our navigation bar view (opaque view blocking the nav bar area to avoid the island effect when transparent) needs to live above the content view in the hierarchy, making the content view the same height as it was before. A surgical spot to put the guard view is up at the root view (PhoneWindow.DecorView). fitSystemWindows is always called since this view is not recreated, and the layout is stable: waiting until the IME is attached to the window is too late to add a guard view. This is above the screen_* layouts, so will work without having to touch all of them. And it only affects windows of TYPE_INPUT_METHOD. Bug:11237795 Change-Id: I6a93f30aec83f1cecfb854073046cbc87ab4aa66
Diffstat (limited to 'docs/html/develop')
0 files changed, 0 insertions, 0 deletions