[jve]

From article:

> Users on such networks might be shown the “did you mean” infobar on every single-term search. To work around this, Chromium needs to know if it can trust the network to provide non-intercepted DNS responses.

Don't know if this is the sole reason.

[1vuio0pswjnm7]

I think you are right.

Reminds me of the story behind "Google Public DNS". Back in 2008/2009, OpenDNS was hijacking "queries" (NXDOMAIN) typed in the address bar to their own search page ("OpenDNS Guide", or some such) on an opendns.com subdomain. In response, Google launched its own open resolver.^1 (OpenDNS was later acquired by Cisco)

1. http://umbrella.cisco.com/blog/opendns-google-dns

[Taek]

In my mind it's a good enough reason to justify trying to fix it.

[ogurechny]

No, the point is that in combined address and search bar you don't know whether something is a (local) domain or a search query. You can recognize known TLDs, but that's it.

Guess what Google' priorities were when they approached that problem.