Yep, visible URL is the right thing to show in the omnibox.  Make sure to also listen to DidAccessInitialDocument to know when to clear it if a malicious page tries to modify the empty page during a load in a new tab, or a URL spoof will be possible.  (There's tons of background on this in  issue 9682 .)

tedchoc@, how should I generally triage Android N bugs?  Is there an appropriate hotlist?

Is this only applicable to N?  Based on the steps, this sounds like it might apply to all android versions.

We use the same logic as desktop for the text to be shown:
https://cs.chromium.org/chromium/src/chrome/browser/ui/toolbar/chrome_toolbar_model_delegate.cc?l=47

Via the Android shim:
https://cs.chromium.org/chromium/src/chrome/browser/ui/android/toolbar/toolbar_model_android.h?ssfr=1&l=22

DidAccessInitialDocument triggers a NavigationStateChanged(INVALIDATE_TYPE_URL)
https://cs.chromium.org/chromium/src/content/browser/web_contents/web_contents_impl.cc?type=cs&q=DidAccessInitialDocument&l=4567

Which should be getting up to java:
 https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/tab/TabWebContentsDelegateAndroid.java?q=NavigationStateChanged+file:android&dr=CSs&l=239

ToolbarManager:
https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/toolbar/ToolbarManager.java?dr=CSs&q=ToolbarManager.java&l=324

LocationBar:
https://cs.chromium.org/chromium/src/chrome/android/java/src/org/chromium/chrome/browser/omnibox/LocationBarLayout.java?dr=CSs&q=LocationBarLayout.java&l=2222

So to me, it looks like we are using the same logic as desktop and listening for the right signal.

Well, I cannot reproduce this on my Android L device on Chrome 56 or on my desktop.

reporter: what version of Chrome are you running?

56.0.2924.87 (Official Build) (32 bit), and I just verified that I can still reproduce it only Nexus.

askatte@, can you try to repro?  Thanks.

Not able to repro this issue on Nexus 6P/ N4F26J / 56.0.2924.87 (Official Build) (32 bit). Followed steps from #0.

Lowering priority. Does not appear to be reproducible, much less widespread.

liaoyuke@, can you reproduce this on a current Chrome release?

@liaoyuke -- Could you please respond to Comment# 10 and update the issue which would help us triage the issue further.
Thanks in Advance.

No replies from the reporter (liaoyuke@); closing as not reproducible.