That's a nice spoof! Definitely reproducible on Android. 
Let me route it to the right team to see if this is an known issue. 
Thanks for reporting!

+spqchan@, could you help me triage this bug since you're quite active in both components?

Thanks!

Sorry jialiul, while I'm active in both the omnibox and fullscreen, I'm only active on Mac. I have no idea how to triage for Android

+tedchoc@, could you help triage this issue since you have worked on omnibox related issues on Android? Please feel free to suggest other owner. Thanks!

Yeah, I'll take a look at this.

tedchoc: Uh oh! This issue still open and hasn't been updated in the last 14 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

tedchoc: Uh oh! This issue still open and hasn't been updated in the last 28 days. This is a serious vulnerability, and we want to ensure that there's progress. Could you please leave an update with the current status and any potential blockers?

If you're not the right owner for this issue, could you please remove yourself as soon as possible or help us find the right one?

If the issue is fixed or you can't reproduce it, please close the bug. If you've started working on a fix, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/a55c2fdf48fb379f994e21768f517b53837ea663

commit a55c2fdf48fb379f994e21768f517b53837ea663
Author: tedchoc <tedchoc@chromium.org>
Date: Tue Sep 27 06:11:07 2016

Keep top controls visible if SHOW is called right after HIDE.

Currently, we early exit if the visibility amount matches our
desired ending amount.  But when you set HIDDEN as the current,
it will start an animation, and a immediate call to SHOWN will
see that the ending condition is met and return, but does not
clear the animation.

Now, clear the animation if the current value matches our
desired ending value to ensure it doesn't move.

BUG= 639702 
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review-Url: https://codereview.chromium.org/2372713004
Cr-Commit-Position: refs/heads/master@{#421125}

[modify] https://crrev.com/a55c2fdf48fb379f994e21768f517b53837ea663/cc/input/top_controls_manager.cc
[modify] https://crrev.com/a55c2fdf48fb379f994e21768f517b53837ea663/cc/input/top_controls_manager_unittest.cc

Your change meets the bar and is auto-approved for M54 (branch: 2840)

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0f76844ee3219d0e3990216b5dd657aac4d36f7b

commit 0f76844ee3219d0e3990216b5dd657aac4d36f7b
Author: Ted Choc <tedchoc@google.com>
Date: Tue Sep 27 17:05:25 2016

Keep top controls visible if SHOW is called right after HIDE.

Currently, we early exit if the visibility amount matches our
desired ending amount.  But when you set HIDDEN as the current,
it will start an animation, and a immediate call to SHOWN will
see that the ending condition is met and return, but does not
clear the animation.

Now, clear the animation if the current value matches our
desired ending value to ensure it doesn't move.

BUG= 639702 
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review URL: https://codereview.chromium.org/2371223002 .

Review-Url: https://codereview.chromium.org/2372713004
Cr-Original-Commit-Position: refs/heads/master@{#421125}
Cr-Commit-Position: refs/branch-heads/2840@{#546}
Cr-Branched-From: 1ae106dbab4bddd85132d5b75c670794311f4c57-refs/heads/master@{#414607}

[modify] https://crrev.com/0f76844ee3219d0e3990216b5dd657aac4d36f7b/cc/input/top_controls_manager.cc
[modify] https://crrev.com/0f76844ee3219d0e3990216b5dd657aac4d36f7b/cc/input/top_controls_manager_unittest.cc

Congratulations - $1,000 for this one!

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/0f76844ee3219d0e3990216b5dd657aac4d36f7b

commit 0f76844ee3219d0e3990216b5dd657aac4d36f7b
Author: Ted Choc <tedchoc@google.com>
Date: Tue Sep 27 17:05:25 2016

Keep top controls visible if SHOW is called right after HIDE.

Currently, we early exit if the visibility amount matches our
desired ending amount.  But when you set HIDDEN as the current,
it will start an animation, and a immediate call to SHOWN will
see that the ending condition is met and return, but does not
clear the animation.

Now, clear the animation if the current value matches our
desired ending value to ensure it doesn't move.

BUG= 639702 
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel

Review URL: https://codereview.chromium.org/2371223002 .

Review-Url: https://codereview.chromium.org/2372713004
Cr-Original-Commit-Position: refs/heads/master@{#421125}
Cr-Commit-Position: refs/branch-heads/2840@{#546}
Cr-Branched-From: 1ae106dbab4bddd85132d5b75c670794311f4c57-refs/heads/master@{#414607}

[modify] https://crrev.com/0f76844ee3219d0e3990216b5dd657aac4d36f7b/cc/input/top_controls_manager.cc
[modify] https://crrev.com/0f76844ee3219d0e3990216b5dd657aac4d36f7b/cc/input/top_controls_manager_unittest.cc

This bug has been closed for more than 14 weeks. Removing security view restrictions.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot