Opened 5 years ago

Closed 2 years ago

#14081 closed task (wontfix)

Contrast our cookie strategy with other leading browsers

Reported by: michael Owned by: tbb-team
Priority: Low Milestone:
Component: Applications/Tor Browser Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: #3246 Points:
Reviewer: Sponsor:

Description

We might want to copy (or at least understand) the high level concept logic behind cookie handling of other leading browsers. Create a wiki linked spreadsheet or CSS table displaying color coded cookie features and defaults.

Example use case

Question: Should we consider JS popups to be child windows (thus 3rd party context) or instantiate new DOMs for them (thus 1st party context?)
Answer: All other browsers consider them child windows so we should as well.

Child Tickets

Change History (3)

comment:1 Changed 5 years ago by michael

Some (like here or there) are commenting about Safari's third party cookie control, whose logic could be relevant.

comment:2 Changed 4 years ago by mikeperry

Keywords: TorBrowserTeam201503 removed

comment:3 Changed 2 years ago by gk

Resolution: wontfix
Status: newclosed

No need for those tickets on our side anymore as Mozilla implemented double-keying of cookies which we ship in 7.0a3 when we switch to ESR 52.

Note: See TracTickets for help on using tickets.