Closed Bug 793454 Opened 12 years ago Closed 12 years ago

Cookie deletion not working on FF15.0.1 - Win

Categories

(Firefox :: Security, defect, P1)

15 Branch
x86_64
Windows 7
defect

Tracking

()

RESOLVED WORKSFORME
Firefox 16

People

(Reporter: me, Unassigned)

Details

Attempting to delete cookies using two separate dialog pathways fails in FF 15.0.1 (Windows 7 64-bit).

Firefox | Options | Options | Privacy tab | Show Cookies | Cookie (modal box) | Remove All Cookies - fails to purge cookies, as opening this dialog a second time yields the same persistent cookies

Firefox | History | Clear Recent History | Clear All History (modal box) | Cookies (checked) | Clear Now (button) - fails to purge cookies as checked again using above pathway
This works for me as expected with Build identifier: Mozilla/5.0 (Windows NT 6.1; rv:15.0) Gecko/20100101 Firefox/15.0.1
Component: General → Security
Duro, can you reproduce this issue with a clean profile?
http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
Flags: needinfo?(me)
I've just checked another user profile on the same machine (though I'd note that FF has upgraded itself to 16.0.1), and this seems to work as I'd expect.

Are there any diagnostics regarding the problematic profile that would be useful for you folks to know?
Flags: needinfo?(me)
Duro, can you reproduce this issue with the problematic profile on Firefox 16.0.1 (or 16.0.2)?

Please also try to reproduce this issue on the latest Nightly ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-central/ (Be advised that Nightly builds are not as stable as released versions of Firefox).
Flags: needinfo?(me)
Yep, it's still a problem with this profile on 16.0.2.
Flags: needinfo?(me)
And tested against the latest nightly firefox-19.0a1.en-US.win32.installer (downloaded today 5th Nov 2012) it seems to have solved the problem - so in FF19.0a1 I am able to delete cookies, Yay!
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.