You’re raising interesting questions that will need input from design.
In the browser use case, design would like to have the chrome follow the OSK when animated in (see bug #1119331). At the moment this is not possible, since all we know from the keyboard is its bounding rectangle in window coordinates. We cannot anchor to it directly. As a result, the chrome bar is animated upwards first, followed by the OSK. This feels odd (but I guess we can learn to live with it).
You’re raising interesting questions that will need input from design.
In the browser use case, design would like to have the chrome follow the OSK when animated in (see bug #1119331). At the moment this is not possible, since all we know from the keyboard is its bounding rectangle in window coordinates. We cannot anchor to it directly. As a result, the chrome bar is animated upwards first, followed by the OSK. This feels odd (but I guess we can learn to live with it).