这是indexloc提供的服务,不要输入任何密码
Skip to content

Request for position: First-Party Sets #93

@cfredric

Description

@cfredric

Request for position on an emerging web specification

Information about the spec

Design reviews and vendor positions

Anything else we need to know

First-Party Sets proposes a new web-platform mechanism to declare that a collection of related domains is a First-Party Set.

This proposal has previously been discussed in PrivacyCG and WebKit has indicated a position in May 2022. However, the First-Party Sets proposal has undergone some significant changes since that position was published, in particular:

  • We've introduced the notion of "subsets" to categorize set member domains, and allow the UA to handle them differently and impose different requirements according to their declared type.
  • We've abandoned the SameParty cookie attribute.
  • We've indicated support for the Storage Access API for sites to request cross-site cookie access, within the bounds of a First-Party Set.

These changes were introduced in WICG/first-party-sets#92. They align the proposal with other browsers' approaches of using the Storage Access API to mediate sites' requests for cross-site cookie access.

Given the extent of the changes (particularly as they relate to some more recent WebKit comments), I'd like to request a "re-"review of the First-party Sets proposal. Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    concerns: complexityThis proposal seems needlessly complexconcerns: privacyThis proposal may cause privacy risk if implementedconcerns: usabilityThis proposal will create usability issues for usersfrom: GoogleProposed, edited, or co-edited by Google.position: opposetopic: privacyvenue: WICGProposal is incubated in the Web Incubator Community Group

    Type

    No type

    Projects

    Status

    Done

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions