Closed Bug 1409574 Opened 7 years ago Closed 7 years ago

"switch to tab" missing or sorted lower in the list in recent nightly builds

Categories

(Firefox :: Address Bar, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID
Tracking Status
firefox57 --- affected
firefox58 --- affected

People

(Reporter: asa, Unassigned)

Details

(Keywords: regression)

switch to tab is missing or sorting too low in the autocomplete list in recent nightly builds. steps to reproduce: 1. open twitter.com 2. open a new tab 3. in the new tab start typing twitter results: the open tab doesn't show up in the autocomplete results or if it does show up it's near the bottom of the results. expected results: the switch to open twitter tab item should be near the top of the autocomplete list.
I first started seeing this in 57 a few weeks before 58 branched. I'm still on 57 now (Developer Edition) and seeing it.
are the results above switch to tab normal history/bookmark results? Switch to tab has always been mixed up with other results depending on the frecency of the page, nothing changed there. For example for me it's the third result (first 2 are specific tweets I probably visited recently). There is an old bug about giving these results some kind of bonus in frecency, but nothing should have changed regarding the order until yesterday's Nightly.
I think what made it noticeable is if you had open tabs, they were *always* in the search results. Sometimes you had to scroll a ways to find them, but they were there. Now the search results are getting limited to the top 10 or 15 hits or something like that, which often places the open tabs off the bottom and not in the list at all. So the change that made this noticeable was probably dropping the upper limit on the number of results listed.
Asa, can you reproduce in the latest Nightly? I think we backed out the patch that was causing this.
Flags: needinfo?(asa)
Indeed this is working again on Nightly. Resolving.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(asa)
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.