If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Privacy - Never remember History Still Remembers Some




Bookmarks & History
5 years ago
5 years ago


(Reporter: Aaron, Unassigned)


16 Branch
Windows 7

Firefox Tracking Flags

(Not tracked)




5 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20100101 Firefox/16.0
Build ID: 20121024073032

Steps to reproduce:

I selected Tools > Options > Privacy and selected never remember my history a while ago but it seems to remember some of the URLs.

Actual results:

When typing in a w into the URL at least 10 previously visited sites appear as suggestions even when never remember history is selected and even after clearing the browser history is used. These are sites I've visited in the past and still remain there after shutdown / reboot etc.

Expected results:

I would have expected there to be no suggestions when typing in urls with the never remember history option is selected, especially after browser history is deleted using the suggested option underneath the setting.

Just to be clear, the suggested sites are not ones visited since starting firefox but look like they are from a long time ago.
this is not security-sensitive, and there appear to be several similar bugs to this already open
Group: core-security


5 years ago
Component: Untriaged → Bookmarks & History

Comment 2

5 years ago
Aaron, do you have any add-ons installed on your Firefox?

Can you reproduce this issue on a profile without those add-ons?
Flags: needinfo?(nospam)
before enabling "never remember history" you should clear history. The former doesn't include the latter.

Comment 4

5 years ago
Sorry I'm being a noob. The auto complete is getting URL's from my bookmarks and I was getting confused.
Last Resolved: 5 years ago
Flags: needinfo?(nospam)
Resolution: --- → INVALID
That makes sense, remember when in doubt you can search in the Library or sidebar to find entries. Thanks for handling the report.
You need to log in before you can comment on or make changes to this bug.