Moving floating keyboard to edge will move it to adjacent display.
This isn't an ideal UX, although there is currently no defined UX for this and this mostly just lays the foundation of any future implementation. When the actual touch point (where the user's finger is) approaches within 10 pixels of the display edge where there is another display attached, the keyboard will transfer to the new display in a default location. This uses a similar mechanism as the ContainerBehavior change, where the new display is queued on the KeyboardController and the keyboard is then hidden. The HideAnimationFinished handler will then check for any queued display changes, and re-open the keyboard on the new display. Bug: 828701 Change-Id: I7d513791b5bd2de9133f6014469cd03c3fa44899 Reviewed-on: https://chromium-review.googlesource.com/1009507 Commit-Queue: Blake O'Hare <blakeo@chromium.org> Reviewed-by:Yuichiro Hanada <yhanada@chromium.org> Cr-Commit-Position: refs/heads/master@{#550126}
Showing
Please register or sign in to comment