localStorage (and generally any DOMStorage we currently have) can be used to store values that are actually very similar by behavior and exploitation to http cookies. On several places we are missing a way to track these localStorage cookie values and delete them along with http cookies in some cases. This bug tracks these issue. One important distinction: a web site (specified by an URL) can behave as an 'offline web application'. This happens after a page presents it self like that AND user gives that site the 'offline web application' permission to act like that. For sites with this permission localStorage values are no longer considered "localStorage cookies" and therefor for those this bug doesn't apply. This is fixed since Gecko 1.9.2, if I have a correct track here, for sure in the up-to-date Gecko version.

Jan: is this something we still want to do?

Hm, I've never heard about this before. Honza, do you remember why we wanted to do this ?

I parse comment 0 to be surrounding the clearing of localStorage data. We've since unified our treatment of "Cookies and Site Data" in about:preferences and are not depending on users to understand the nuances between HTTP cookies and localStorage, so I think it makes sense to resolve this as WORKSFORME. In regards to 'offline web application', I think that's a moot thing given the rationale behind the "Cookies and Site Data" and the related spec work about boxes and storage.

(In reply to Andrew Sutherland [:asuth] from comment #3) > I parse comment 0 to be surrounding the clearing of localStorage data. > We've since unified our treatment of "Cookies and Site Data" in > about:preferences and are not depending on users to understand the nuances > between HTTP cookies and localStorage, so I think it makes sense to resolve > this as WORKSFORME. In regards to 'offline web application', I think that's > a moot thing given the rationale behind the "Cookies and Site Data" and the > related spec work about boxes and storage. Agree, thanks!