Clear history does not clear localstore.rdf

RESOLVED WORKSFORME

Status

()

Core
History: Global
--
enhancement
RESOLVED WORKSFORME
16 years ago
14 years ago

People

(Reporter: Rembert Oldenboom, Assigned: Blake Ross)

Tracking

Trunk
x86
Linux
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1a) Gecko/20020610
BuildID:    2002061108

Hitting the Clear History button does clear the history.dat file correctly but
not the history.db file. This is a possible privacy risk.

Reproducible: Always
Steps to Reproduce:
1.Go surfing
2.Hit Clear History button
3.Check history.db in the .mozilla dir

Actual Results:  History.dat file is empty, history.db not

Expected Results:  I expected it to be empty
reporter (Rembert Oldenboom): can you reproduce this bug with a recent build of
mozilla (for example, 1.1beta)? if so, please comment again with details. if
not, please resolve this bug as WORKSFORME. thanks.
(Reporter)

Comment 2

16 years ago
Checked with 1.1b. Same steps followed. history.db is not created nor filled anymore. Browsing history is now also written to localstore.rdf at nc:urlbar-history. Hitting the clear-history button does not clear this part of localstore.rdf so the possible privacy risk remains.
PS. Replaced 'history.db' with 'localstore.rdf' in Summary line.
Summary: Clear history does not clear history.db → Clear history does not clear localstore.rdf

Comment 3

15 years ago
Um, 'Clear Location Bar' on the same pref panel as 'Clear History' is 
what will clear the entries in localstore.rdf. That's the same UI that
Nav4.x had, although I suppose it might be simpler to just combine the
two functions as is done in IE.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 4

14 years ago
Rembert, so this works, right?
(comment #3)

Comment 5

14 years ago
WFM
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.