[Bug 209794] Re: "Clear Private Data" does not clear private data from the Awesome Bar's Rich Results list

[zaza1851983]

Very good, that was stupidity on my side, but still interesting to notice that this check box was by default unchecked. 
And then of course, I still have the problem like everybody else, that is after clearning the private data, nothing is removed, and no new history is added :)


--- On Tue, 10/14/08, Mackenzie Morgan <macoafi at gmail.com> wrote:

> From: Mackenzie Morgan <macoafi at gmail.com>
> Subject: Re: [Bug 209794] Re: "Clear Private Data" does not clear private data from the Awesome Bar's Rich Results list
> To: zaza1851983 at yahoo.com
> Date: Tuesday, October 14, 2008, 11:19 AM
> On Tue, 2008-10-14 at 21:46 +0000, zaza1851983 wrote:
> > I got a similar problem, only a little bit different,
> I don't know if
> > this the right place to post it, but I'l do it
> anyway. The problem is
> > that I don't get the clear private data window at
> all, whenever I click
> > shift+ctrl + del or Tools-> clear private data,
> simply nothing happens.
> > Does anyone else have this problem?
> 
> Any chance you unchecked "Ask me before clearing
> private data" in the
> Preferences?
> 
> -- 
> "Clear Private Data" does not clear private data
> from the Awesome Bar's Rich Results list
> https://bugs.launchpad.net/bugs/209794
> You received this bug notification because you are a direct
> subscriber
> of the bug.
> 
> Status in “firefox-3.0” source package in Ubuntu:
> Triaged
> 
> Bug description:
> Steps to Reproduce:
> 1. Navigate to a few websites
> 2. Tools -> Clear Private Data
> 3. Begin to type into the address bar the name of a site
> you visited before
> 
> Expected results:
> The site is not recognized because private data was
> cleared.
> 
> Actual results:
> Your browsing habits are clearly visible in the dropdown
> from the address bar.

-- 
"Clear Private Data" does not clear private data from the Awesome Bar's Rich Results list
https://bugs.launchpad.net/bugs/209794
You received this bug notification because you are a member of Mozilla
Bugs, which is a bug assignee.