Deleting the most recent visit to a site from history resets its priority for the location bar autocomplete




9 years ago
6 years ago


(Reporter: rfugger, Unassigned)



Firefox Tracking Flags

(Not tracked)




9 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20091109 Ubuntu/9.10 (karmic) Firefox/3.5.5

When I delete the most recent visit to a frequently-visited site from my history, the site no longer comes up at or near the top of the location bar when I type in the first few letters.  These are sites that I visit every day and should be coming up at the top even if I hadn't visited them for a day.  

Immediately after deleting, the sites don't appear at all in the location bar autocomplete, even though they appear many times in the history.  When I manually enter the URL for one of the sites, it seems to start back into the autocomplete system as though it was a completely new site with no visits.

Reproducible: Always

Steps to Reproduce:
1. Find a history item that comes up in top spot for a location bar autocomplete of a certain string based on past days' visits.
2. Go to that site.
3. Go to history and delete the item "Today", erasing all history items for the current day.
4. Attempt to bring up the same history item from step 1 based on the same autocomplete search string.
Actual Results:  
Item that used to be at the top of the autocomplete list is now missing.

Expected Results:  
Item should still be there based on previous days' visits.
i can guess what happens here.
when you remove the visit we mark the frecency of the url (the value uesd for autocomplete ordering) as to be recalculated, then until it's recalculated it will appear below other urls with valid frecencies.
PS: out of curiosity, what's the use case about removing the last visit for a page that has lots of visits in the past?
hm also, actually, when you remove a page from history, regardless its position (today, yesterday) i think we are removing all entries to preserve privacy.
you probably want to use Clear Recent History instead?

Comment 4

9 years ago
> PS: out of curiosity, what's the use case about removing the last visit for a
> page that has lots of visits in the past?

If someone else has been browsing and I don't want my history polluted with their stuff, it seems easy to get rid of their activity by just deleting the whole day, rather than go through item by item.

If clear recent history does this, then that's news to me.  I thought it would just clear the whole history like it did last time I tried in 3.0 (or 2.0?).
Clear Recent History will delete the amount of history you want, last hour, last 2 hours, last 4 hours, today, everything
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.
Whiteboard: [CLOSEME 2011-1-30]
Version: unspecified → 3.5 Branch

Comment 7

8 years ago
Yes, still occurs in 3.6.13.
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE

Comment 9

8 years ago
Still occurs with new profile in 3.6.13.
Component: Location Bar → Bookmarks & History
QA Contact: → bookmarks
Resolution: INCOMPLETE → ---
Whiteboard: [CLOSEME 2011-1-30]
Version: 3.5 Branch → 3.6 Branch
Able to reproduce on Mozilla/5.0 (Windows NT 5.1; rv:12.0a1) Gecko/20111230 Firefox/12.0a1 ID:20111230031151

but comment 3 seems to mean this should be Resolved/Invalid as Firefox intentionally deletes all history for the given site.
Version: 3.6 Branch → Trunk

Comment 11

6 years ago
I have the same issue.  The site that always appears in my drop down history is

But I don't even know that site? What should I do?
Show all history, search for ycabda and remove entries
I think the use case expressed in comment 4 is better served by private-browsing (with per-window PB it's even easier).
Comment 1 explanation still applies here, and it's expected behavior.
Last Resolved: 8 years ago6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.