I'm thinking nsICookieManager2 is where this should live. See the dependencies for a couple of places where this would be used.
yeap... do you wanna implement this? (please do the UI concurrently though, we don't want a bloaty method hanging around with no consumers)
darin raised a good point, if we're going to clear session cookies when Mozilla still thinks there's an active session for memory cache/SSL connections, we could break some sites that rely on a session being more than just a cookie. (i.e. if the SSL session coexists with a secure cookie, does clearing the cookie have adverse effects on that too?) At this stage of "sustained Seamonkey developement" I don't think its really viable/desired to put a lot of work into implementing something that's seamonkey-specific. However, for Firefox it might be useful to have Work Offline clear all session data, I need to get feedback from ben on whether that's needed/desired. So, I'm going to leave this out there because I can see viable uses for it, but I don't think we'll end up implementing anything using it in seamonkey. (and yes, I'm going to do it myself or I wouldn't have filed it on myself.)
Not going to be working on any Seamonkey UI bugs for the foreseeable future. You can filter on "danlikesgoats" to delete this spam.
Assignee: mconnor → nobody
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.