"Most Visited" in the Bookmarks Toolbar and "Most Visited" in the Library can contain different entries

RESOLVED WORKSFORME

Status

()

Firefox
Bookmarks & History
--
minor
RESOLVED WORKSFORME
7 years ago
4 years ago

People

(Reporter: luitzen, Unassigned)

Tracking

3.6 Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

7 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8

It looks like redirectsMode = 0 in the last case.

Reproducible: Sometimes

Steps to Reproduce:
1. Be sure that your browser history contains a lot of entries, including redirecting-to and redirecting-from pages.
2. Try to remember all entries in "Most Visited" (from Bookmarks Toolbar).
3. Try to find these entries in "Most Visited" (from Library).
Actual Results:  
Not all entries are found

Expected Results:  
All entries are found

Updated

7 years ago
Version: unspecified → 3.6 Branch
Is this still an issue? Firefox 4 RC is out, and soon will be final, would be cool to know if that's still reproduceable.
Actually the two queries are exactly the same, I could only guess this could happen when 2 pages have the same count and sqlite could decide to sort them based on something other, but this should have been fixed some time ago.
(Reporter)

Comment 2

7 years ago
Created attachment 520888 [details]
Firefox 4.0 RC2

It seems it is not fixed in 4.0 (RC 2).
Unfortunately, titles of pages are in Russian (as well as the interface), but lists of favicons differ.
Mozilla/5.0 (Windows NT 5.1; rv:23.0) Gecko/20100101 Firefox/23.0
Mozilla/5.0 (Windows NT 5.1; rv:25.0) Gecko/20100101 Firefox/25.0

This is no longer an issue on latest Nightly (buildID: 20130805030205) and Firefox 23RC (buildID: 20130730113002).
Status: UNCONFIRMED → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.