Closed Bug 689724 Opened 14 years ago Closed 13 years ago

Location Bar History Sort Order changed with Firefox 7

Categories

(Firefox :: Bookmarks & History, defect)

7 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: dennis.schieferdecker, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0) Gecko/20100101 Firefox/7.0 Build ID: 20110922153450 Steps to reproduce: I updated from Firefox 6.0.1 to Firefox 7.0. Actual results: The order in which the dropdown menu of the location bar displays previously visited websites changed completely. Now, sites that weren't visited very often appear before frequently visited sites. Probably either the algorithm to rank the sites or how site frequencies are counted was changed. I assume that site reloads or hits on subpages of a site are now also counted towards the overall frequency of the site. Expected results: The order in which the dropdown menu of the location bar displays previously visited websites should not have changed just by a browser update. Alternatively make the websites' frequency counter visible or announce that and how the ranking algorithm has changed.
Component: Location Bar → Bookmarks & History
QA Contact: location.bar → bookmarks
afaict nothing was changed in Firefox 7 regarding such ordering.
My dropdown menu for the location bar is also behaving strangely since I updated to Firefox 7 at work. Google became the #4 link on my bar when it should be the first one by far
Hello, I have the same problem.
I have the same problem too.
Hello agian, In Firefox 8.0 this problem still occurs !!!
This affects me also, and even though it's a minor thing, it's annoying the heck out of me because I use it every day! Just upgraded to Firefox 8.0 and still have the issue.
This is annoying the heck out of me, too.
nothing easy to debug, it's possible some dbs got corrupted and history was reset as a consequence
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.