Closed Bug 333591 Opened 18 years ago Closed 18 years ago
Clear Private Data does not clear Saved Form Information
Steps to reproduce: - Set Clear Private Data to set Saved Form Information on close - Restart Firefox - The form information is still there NB: In the Privacy > Saved Form tab in the Options window this button is grayed out. I'm nearly positive that I reported this before, but I can't find the bug so I think it is closed but the problem is still there.
18 years ago
Assignee: nobody → pamg.bugs
Priority: -- → P1
Target Milestone: --- → Firefox 2 alpha2
Confirming bug! Still seeing this in the latest branch build: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20060414 Firefox/2.0a1 ID:2006041410
This is still the case in the places-less branch builds (I still see the sqlite file in the branch profile).
There's a bug to switch back to using Mork for form history on the branch, though I'm not sure what's up there. Brett, care to fill in the blanks here?
*** Bug 336815 has been marked as a duplicate of this bug. ***
retargetted at beta1
Target Milestone: Firefox 2 alpha2 → Firefox 2 beta1
Can't we just have 'Saved Form Information' clear 'formhistory.sqlite' as well if it exists?
I've confirmed this on nightlies from 1.8 branch (without Places) and trunk (with Places). It appears that the service is not correctly detecting when form information is present. It does need to be fixed for FF2b1, but it's not a Places bug -- not sure which component it properly belongs to.
There is no component Privacy, Security seems exaggerated and only Preferences or General seems to be appropriate.
Can somebody change the OS to all? I see this in my Linux builds as well.
Fixes error in nsStorageFormHistory that caused it to never see form history entries, as well as restoring searchbar.mTextbox so sanitize.js can clear it.
Attachment #222277 - Flags: review?(bryner)
Comment on attachment 222277 [details] [diff] [review] Fixes two problems producing this bug mFoo is generally a convention for private member variables, so I think using it here is a bad idea (especially since there already is a "private" member _textbox). I think a better solution would be to name the property just "textbox" and change sanitize.js to match.
Attachment #222277 - Flags: review?(bryner) → review-
(In reply to comment #11) > I think a better solution would be to name the property just "textbox" and > change sanitize.js to match. Done.
Attachment #222284 - Flags: review?(bryner) → review+
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.