: New feature! MozillaWiki is now mobile-friendly. Visit from a mobile device to see new mobile theme + try editing. Release details.

Browse wiki

Jump to: navigation, search
Privacy/Features/Multiple Cookie Jars
Feature accessibility lead `  +
Feature accessibility notes `  +
Feature accessibility review `  +
Feature accessibility status `  +
Feature additional members `  +
Feature dependencies `  +
Feature engineering notes `  +
Feature engineering status `  +
Feature engineering team Privacy  +
Feature feature manager Sid Stamm  +
Feature functional spec `  +
Feature health OK  +
Feature implementation notes `  +
Feature implementation plan `  +
Feature landing criteria `  +
Feature lead engineer `  +
Feature list `  +
Feature localization lead `  +
Feature localization notes `  +
Feature localization review `  +
Feature localization status `  +
Feature name Multiple Cookie Jars  +
Feature non-goals `  +
Feature open issues and risks `  +
Feature operations lead `  +
Feature operations notes `  +
Feature operations review ` +
Feature operations status `  +
Feature overview For many parts of the browser, including a
For many parts of the browser, including add-ons, it would be nice to maintain a separate cookie store or cookie jar. Currently the cookie service only allows one place (and one set of all cookies for a domain) but some features would benefit from having a different "profile" of cookies depending on the context in which the HTTP requests go out.
context in which the HTTP requests go out.  +
Feature priority P1  +
Feature privacy lead Sid Stamm  +
Feature privacy notes `  +
Feature privacy review `  +
Feature privacy status `  +
Feature product manager Sid Stamm  +
Feature product marketing lead `  +
Feature product marketing notes `  +
Feature product marketing status `  +
Feature products notes `  +
Feature products status `  +
Feature project `  +
Feature qa lead `  +
Feature qa notes `  +
Feature qa review `  +
Feature qa status `  +
Feature rank 2  +
Feature requirements * Backwards compatible: things assuming one cookie jar must still operate without code change. * Arbitrary jarring: add-ons should be able to construct and use their own cookie jar.  +
Feature roadmap Privacy  +
Feature secondary roadmap Platform  +
Feature security health `  +
Feature security lead `  +
Feature security notes `  +
Feature security review `  +
Feature security status `  +
Feature stage Draft  +
Feature status `  +
Feature status note `  +
Feature theme Contextual Identity  +
Feature users and use cases # Safe Browsing traffic uses a cookie to m
# Safe Browsing traffic uses a cookie to make sure quality of service is adequate and abuse of the system goes mitigated. There's no reason cookies for the Safe Browsing service to be shared with those used by general traffic to Google properties (e.g., log into gmail). The Safe Browsing service could still operate properly if its cookies were separate from the rest of the user's http cookies, and the isolation of identification tokens would increase our users' control over HTTP-borne identifiers.
sers' control over HTTP-borne identifiers.  +
Feature ux design We should revamp the Cookie UI to present multiple jars (if they're deployed) or change the delete-individual-cookies UI to make it clear which jar each cookie is in.  +
Feature ux lead `  +
Feature ux notes `  +
Feature ux status `  +
Feature version `  +
Categories Feature Page
Modification date
This property is a special property in this wiki.
27 April 2012 20:08:46  +
hide properties that link here 
  No properties link to this page.


Enter the name of the page to start browsing from.