GitLab

As Android doesn't know about Chrome OS System UI, it can place the
PIP window at an incorrect position.
There were CTS concerns that disallow Chrome to adjust PIP initial
bounds, but we decided to workaround this on the Android side.

BUG=b:147790853
BUG=b:147791406
TEST=Manually confirmed PIP windows were located at the correct position
TEST=with hotseat on
TEST=android.server.am.ActivityManagerPinnedStackTests
TEST=#testEnterPictureInPictureSavePosition

Change-Id: Ibe962fc105584a1d457a3e3075e2dcabc23db129
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2022582
Commit-Queue: Kazuki Takise <takise@chromium.org>
Auto-Submit: Kazuki Takise <takise@chromium.org>
Reviewed-by: Stefan Kuhne <skuhne@chromium.org>
Reviewed-by: Mitsuru Oshima (slow in TOK) <oshima@chromium.org>
Cr-Commit-Position: refs/heads/master@{#736894}