388426 - Expired cookie not removed from Cookie Manager when it's open

Status: NEW

(Firefox :: Settings UI, defect)

Description

[Victor Kropp]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.4) Gecko/20070515 Firefox/2.0.0.4

When the Cookies window (Tools -> Options -> Privacy -> Show cookies...) is open and cookie is "removed" (its expiration date set to 01-Jan-1970 GMT), it is not removed from Cookies window.

When cookie with the same name is added later, it appears at the end of list and duplicates the first one.

Reproducible: Always

Steps to Reproduce:
1. Open Cookies window (Tools -> Options -> Privacy -> Show cookies...)
2. Click "Set cookie" on test page, cookie appears in Cookies Manager window.
3. Click "Remove cookie" on test page.
Actual Results:  
Cookie not removed from Cookies Manager window.

Expected Results:  
Cookie should disapear from Cookies window.

Comment 1

[Alastair Battrick]

I can confirm this also happens in
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6

Comment 2

[[e-mail]]

-> firefox/preferences

Comment 3

[Florian Quèze [:florian]]

Inside the file, there is a comment saying:
// We don't yet handle aData == "deleted" - it's a less common case
// and is rather complicated as selection tracking is difficult

http://bonsai.mozilla.org/cvsblame.cgi?file=/mozilla/browser/components/preferences/cookies.js&rev=1.18#113

Comment 4

[Victor Kropp]

Maybe "it's a less common case", but very needed for testing web apps.

Comment 5

[Martin Bay]

Also appears in:
Mozilla/5.0 (Windows; U; Windows NT 5.1; da; rv:1.9.0.5) Gecko/2008120122 Firefox/3.0.5

This bug has caused me, and probably many developers, a lot of unnecessary headache.

Maybe add a "Refresh" button to the cookie manager?

Comment 6

[David Viner]

I have just added my vote for this bug to be fixed as it caused me headaches as well until I realised what was going on. Either a refresh button as Martin Bay suggests or a better "live" update is required to make this a much more useful tool for developers.