Thanks for the report!

What type of keyboard are you using?  Software on-screen?  If so, which one?  Or is it bluetooth hardware?

Also, there should be an flag labeled something like "spannable inline autocomplete".  Try changing the value of the flag and seeing if the problematic behavior still exists.

I am using virtual (on screen) keyboard Gboard 6.4.16

Turning off spannable inline autocomplete restores omnibox to fully working behavior.

Thanks for the quick response.

Handing over the changwan@, as he knows the current state of how this change interacts with various versions of gboard.

I am able to repro this issue once Gboard on test device was updated to 6.4.16.
It didn't repro while I had the older version of Gboard (6.3).

Ok, it doesn't repro once I type a URL and commit. Autocomplete started working back fine after that (Gboard 6.4.16).
I also tried clearing data from Chrome and re-signing in. Autocomplete didn't work initially but started working once I navigated to a URL and tried typing in the same URL again. 

Re #7,

Once you type any URL and commit, do you get autocomplete for other URLs as well? Or do you get autocomplete just for the same URL?

askatte@, could you also run a CL bisect for this? Thanks.

Re #8 - autocomplete works for other URLs or queries from history. Not just that one URL.

I will try more for exact steps and do a CL-bisect if its 100% reproducible on restarting after clearing data.

thank you for the very quick and comprehensive triage of this issue

Unfortunately I was not able to reliably repro this issue even after freshly starting (syncing) Chrome, hence cannot provide bisect info.
But, I also hit it once on another device (Sony Xperia Z1 / 4.4.4 / Xperia keyboard). 

wfh@, do you still run into this when you enable SpannableInlineAutocomplete?

We think that this happens only in certain situations, e.g., after version update or sign-up delayed, but so far we couldn't reliably repro it. If you can confirm it, it would help for us to narrow down the problematic test cases.

A friendly ping! wfh@, I would appreciate it if you could try re-enabling the feature.

I reset all my flags and was able to reproduce this once more today after I think a fresh load, but reloading Chrome made it work again... I was using Canary 62.0.3194.0

Can you be more specific as to exactly you want to test?

Also, can you confirm that no data is being sent to 'gboard' when I am in incognito - especially no data is being sent off the device to Google? I would assume that when I am in incognito mode then no keystrokes would be being sent i.e. no autocomplete based on anything not already on the device (e.g. URLs).

yukawa@, could you answer the question at #15? Chrome did the work at issue 725543. (Marking RVG just in case).

I mean regarding incognito mode support on Gboard.

I just sat down with wfh@ to try to reproduce this issue, but we couldn't.

wfh@ said that he experienced this only twice, once on Aug 11 and once yesterday (with the default flag). I also checked that his gboard does not underline text at all.

He reset the flag a while ago, and rebooted the phone a few times, so that might have affected the reproducibility. We also tried resetting the flags and rebooted the phone a couple of times but failed to reproduce this issue. 

Anyways, I appreciate your support on this!

However, at this point, it isn't clear whether or not it is the new model that caused this because reproducibility seems affected by flag change.

changwan@: I've filed b/65081367 for that.

Removing RVG as the question regarding Gboard was split into b/65081367.

This happened again today 

63.0.3204.0 (Official Build) canary (32-bit)
Android 8.0.0; Pixel XL Build/OPR6.170623.011

Omnibox does not autocomplete but interestingly if I type something into the omnibox then task switch away from Chrome then back to Chrome then it will autocomplete whatever was typed in.

WFH informed me about this situation in more detail:

I think it happens when my phone is under heavy load and it background kills tasks
because it often happens after a long Pokemon GO session

Ted, is there an easy way to reproduce background killing? How is it different from cold startup? Any idea on what could have caused this?

Background killing of what?  Turning on "Don't keep activities" kills chrome as soon as you leave, but autocomplete should be entirely within the browser process so I'm not sure what all that helps with.

If you switch away from chrome and come back, we forcefully refocus the omnibox and trigger autocomplete, so that still to me indicates that we weren't requesting autocomplete in the prior case.

changwan@, any update on this blocker?

punted to M63

wfh@, do you still see this issue? It's likely fixed by recent changes.

I think this is a dup of issue 764749, and it should be fixed now by https://chromium-review.googlesource.com/c/chromium/src/+/668196 .

wfh@, when you see this issue again, could you please file a feedback report?