about:omnibox data would help.

It would, for example, clarify whether this is coming from a URL suggestion from history or coming from "navsuggest", which are URL suggestions from the server.

It would also clarify whether the suggestion actually is http://.  For example, on the Android dropdown, we don't show the scheme, so the suggestion looks like www.nextbus.com for me (I visit nextbus regularly, just like Zach) but tapping on it brings me directly to https://www.nextbus.com/.

I can confirm the suggestion is definitely http. :)

To clarify sequence of events:

1.) I manually navigated to "nextbus.com"
2.) nextbus.com does not auto redirect to https://, so it defaults to http
3.) I realize geolocation is not working, and it's probably because not https
4.) I manually focus omnibox and add https:// prefix
5.) geolocation works
6-N.) Every time I type in "nex" in the omnibox, it only (certainly the first) suggests http://nextbus.

Output from about:omnibox (didn't know this existed!) attached.

I think that if we know there is a valid https:// location, we should never be suggesting http.

Deleted: Screenshot_20170816-071920.png 153 KB

	Screenshot_20170816-071920.png 153 KB View Download

Thanks Zach.  In this case, it sounds like bug 542484 ("Omnibox hard to retrain https<->http").  Sadly, the best answer we have for you at the moment is to explicitly select the https suggestion from the dropdown each time.  At some point it'll start winning.