Clear history completely

UNCONFIRMED
Unassigned

Status

()

Firefox
General
UNCONFIRMED
5 years ago
4 years ago

People

(Reporter: John Crisp, Unassigned)

Tracking

({privacy})

26 Branch
x86_64
Linux
privacy
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [bugday-20140127])

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:26.0) Gecko/20100101 Firefox/26.0 (Beta/Release)
Build ID: 20131206152142

Steps to reproduce:

FF 26 / Linux /x64

Attempted to Clear History

I tried clearing cookies, cache and active login expecting that this would be cleaned properly.



Actual results:

it did not remove various session files from profile such as places.sqlite, signons.sqlite, sessionstore.js which included personal data etc.


Expected results:

ANYTHING with personal data should have been cleaned. Clear, should mean CLEAR, not clear what Mozilla feels like clearing.

This resulted in pages where the wrong users name kept on appearing in the login box which could not be cleared, and various issues with javascript being left somewhere in cache which messed up debugging a website.

I was also surprised just how much personal data was residing there in pain view. Unacceptable.

Comment 1

5 years ago
Hi John

Can you tell me how you delete them? From the browser or from profile folder?
Flags: needinfo?(jcrisp)
Whiteboard: [bugday-20140127]
(Reporter)

Comment 2

5 years ago
Hi,

I deleted them manually from the profile folder. There is no way I could see to delete things from the browser
Flags: needinfo?(jcrisp)

Comment 3

4 years ago
> This resulted in pages where the wrong users name kept on appearing in the login box which could not be cleared,

I think that's form history, not signons.

If you have form history disabled, there is a bug that it won't be cleared: bug 942613.

Passwords can be deleted elsewhere: bug 991380.
QA Whiteboard: [bugday-20140505]
Component: Untriaged → General
Keywords: privacy
You need to log in before you can comment on or make changes to this bug.