Remove current_keyboard_bounds() access from LockLayoutManager logic
This also makes the lock screen UIs floating-keyboard-friendly. It seems that the obscuring bounds and workspace displacing bounds don't quite fit the behavior pattern that is needed here, but at the same time, I would like to remove all instances of "keyboard bounds getter + some caller-specific conditional logic" throughout the codebase. So I had to add another getter called GetKeyboardLockScreenOffsetBounds(). Specifically, it seems that WebLoginUi is temporarily overriding the overscroll enable state independent of whether the keyboard is locked. This makes the current bounds getters not 100% applicable. I'd like to revisit this and clean it up a bit, but for now, I'd like to get the one-off logic out of the layout manager and into the KeyboardController so that I can add the floating keyboard condition as well. Bug: 787713 Change-Id: I556941b0fa1e060349c3030a0e08eefb7693314f Reviewed-on: https://chromium-review.googlesource.com/828421 Commit-Queue: Blake O'Hare <blakeo@chromium.org> Reviewed-by:Mitsuru Oshima <oshima@chromium.org> Reviewed-by:
Yuichiro Hanada <yhanada@chromium.org> Cr-Commit-Position: refs/heads/master@{#525277}
Showing
Please register or sign in to comment