URLs of visited sites remain in History after corresponding History entries are deleted

RESOLVED INVALID

Status

()

Firefox
Bookmarks & History
P3
normal
RESOLVED INVALID
3 years ago
a year ago

People

(Reporter: el8, Unassigned)

Tracking

50 Branch
Unspecified
Windows
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

3 years ago
User Agent: Mozilla/5.0 (Windows NT 6.0; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20150320202338

Steps to reproduce:

1. Use a new FF profile (I just didn't manage to figure out under what conditions the bug works - sometimes it doesn't).
2. Open a site, let it be "http://omegle.com" for example.
3. Open the History side bar (Ctrl+H) and delete (via the DEL key or the "Delete This Page" context menu option) the corresponding entry, "Omegle: Talk to strangers!".
3. In the Search bar type "o" (or any other substring of "http://omegle.com").
4. The entry "omegle.com/" will appear. It won't have the site icon on the left, unlike the entry you deleted during step 3, but will be there.

Restarting the browser doesn't help.
If you delete "omegle.com/", it will be gone, but I'm sure that's not how deleting history entires is supposed to work.
(Reporter)

Updated

3 years ago
OS: Unspecified → Windows Vista
(Reporter)

Comment 1

3 years ago
(Sorry for the extra step 3 - I'd edit the message, but I can't now).

Updated

3 years ago
Group: core-security
Component: Untriaged → Bookmarks & History
did you reproduce that in a new profile?
after deleting the entry, if you search omegle in the history sidebar, do you see any entry?

I'd suggest to try this add-on to check the database is not corrupt and coherent. a corrupt database can show this kind of problems.
https://addons.mozilla.org/en-US/firefox/addon/places-maintenance/
(Reporter)

Comment 3

3 years ago
> did you reproduce that in a new profile?
Yes, I used a freshly created profile, to make sure it doesn't have anything to do with extensions, a corrupted DB file and so forth (Step 1 of my first message)
> after deleting the entry, if you search omegle in the history sidebar, do you see any entry?
Yes, that's what I wrote about. If I search for any substring of "http://omegle.com", the "omegle.com/" entry appears.
>I'd suggest to try this add-on to check the database is not corrupt and coherent. a corrupt database can show this kind of problems.
Thanks, I've tried the extension (checked all the checkboxes to perform all the operations), but that didn't help.

Moreover, I installed that latest (40.0.2) version of FireFox (I'm using 36.0.4 because of some software problems), created a new profile there, and watched the same behaviour.
(In reply to el8 from comment #3)
> > after deleting the entry, if you search omegle in the history sidebar, do you see any entry?
> Yes, that's what I wrote about. If I search for any substring of
> "http://omegle.com", the "omegle.com/" entry appears.

I explicitly said to check the history sidebar (not the location bar), if the entry appears in the sidebar then it's possible you didn't remove all the entries for that domain.
(Reporter)

Comment 5

3 years ago
I checked the History sidebar (Ctrl+H), not the Location bar (I know the difference :)
> 3. In the Search bar type "o"
Here I meant the search input field of the History sidebar. Perhaps I used a poor wording, sorry.
Also reproducible in Windows 10 and 7.
OS: Windows Vista → Windows

Comment 7

2 years ago
You encounter this issue because when you open above site, somehow this stores two same URL in history. If you search history sidebar by typing this URL, it will pull up two same URL. Delete both URL, then you won't get this issue. Thanks!
Flags: needinfo?(regspam)

Comment 8

2 years ago
I don't see this issue on Chrome though.
(Reporter)

Comment 9

a year ago
(In reply to Kanchan Kumari QA from comment #7)
> You encounter this issue because when you open above site, somehow this
> stores two same URL in history. If you search history sidebar by typing this
> URL, it will pull up two same URL. Delete both URL, then you won't get this
> issue.
Unfortunately, with this bug still not fixed, every time you need to make sure Firefox does clear a history item, you need to do that extra step after deleting the item in a normal way, which is of course somewhat annoying.
And it's not with "http://omegle.com" only. If delete (Ctrl-A, Del) everything in the History sidebar, and then type a spacebar in the input field, a lot of absolutely unexpected, long-forgotten URLs will pop up (provided you had a rich browsing history).
Version: 36 Branch → 50 Branch

Comment 10

a year ago
Reproducible on Version 	53.0a1
Build ID 	20170104030214
User Agent 	Mozilla/5.0 (Windows NT 10.0; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0
Status: UNCONFIRMED → NEW
Ever confirmed: true
The reason for this is that the history sidebar doesn't show everything in history. In case of redirects it will show the target of the redirects, but not their sources.
When you search, instead we include everything cause you are explicitly searching for something and thus we don't want to "hide" anything.

The basic fact is that the history sidebar is not a privacy tool, it is a navigation tool. Since its scope is allowing to navigate back in history, the view is optimized for that, rather than for privacy management. The only way to be sure you cleared a domain from there is to group it by site and then "Forget about this Site". Or make a search and THEN remove found entries.

Better privacy tools are the Clear Recent History and Private Browsing.

That said, we could evaluate internal smart handling so that when we remove a page we also try to remove redirect sources to it. But for now, please use more appropriate tools to manage your privacy.
Priority: -- → P3
Flags: needinfo?(regspam)
Forget about this Site also appears on single entries, and it's the right privacy option to pick. Delete Page cannot satisfy your privacy needs also cause it only removes the page from history, it doesn't clear other related information about that page (cookies, offline data and such).
(Reporter)

Comment 13

a year ago
Thank you very much for the detailed explanation, Marco.
Status: NEW → RESOLVED
Last Resolved: a year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.