Tracking (and enabler) bug for unified autocomplete. Unified autocomplete is a new Places autocomplete component that will replace "urlinline" and "history" (in the sense of history autocomplete) components. It is basically a merge of the two. The reasoning behind it it's simple, we are going to add further stuff to autocomplete results, doing that with the current splitted components would be tricky, especially for frecency merging. Unified autocomplete is a merge of the two old components, but using more modern and maintainable code (among which promises, Task and Sqlite.jsm). It also contains Top Search providers functionality (that is the primary reason this work is happening).
Running Iceweasel 35.0a2 (with various extensions, including Classic Theme Restorer). Saw this change, thought “that's just WRONG”, headed straight for about:config, found the relevant option and switched it off. Just for the record, I prefer the old behaviour (browser.urlbar.unifiedcomplete = false). I'm not concerned about the actual implementation; just the presence of that unwanted extra item at the top of the autocompletion list.
I have been testing/using Unified Autocomplete (unifiedcomplete) for several months. I strongly prefer it to non-unified autocomplete because when the user types a keyword, the associated URL gets highlighted in the dropdown, providing a visual indication of where pressing Enter will go. Seems essential. Firefox 39.0 (final release) has changed Unified Autocomplete to negate much of the value of that visual feedback. Now, when the user types a keyword, only the host of the URL appears in the dropdown, instead of the name of the Bookmark and the entire URL. The result is that now, even with Unified Autocomplete enabled, the user has no indication of the complete URL that will be requested when they press Enter. The user always needs to know the exact URL that will be loaded when they press Enter.
There are no more P1 blockers to the feature, we can ship it. Remaining bugs will be fixed apart.