WICG/first-party-sets Issues

Last updated Dec 22, 2024, 5:45:59 AM UTC.

This repository doesn't have the Priority: Eventually label that's used to mark an issue as triaged without giving it an SLO. Until that's added, this summary uses heuristics to guess if each issue has been triaged.

Untriaged

Try to triage issues within . [ More Info ]

Issue Title Within SLO On maintainers' plates for Time left Time past SLO
#22 Define parties across W3C considering relationship with one another, trust, choice, scale and varying conditions ❌
#23 Incorporate Transparency and Consent Framework (TCF) 2 ❌
#24 Understand requirements from owners of multiple brands via PRAM and IAB TL ❌
#25 Capture ICANN input ❌
#34 Clarify behavior with subresource requests and subframe navigations ❌
#38 Configuration errors and reporting ❌
#40 Organisation name for the owner ❌
#41 Align First Party Sets debate to the position of G7 regulators ❌
#48 Scaling issues with non-automated verification process ❌
#51 Policing FPS ❌
#55 FPS as an attack surface ❌
#64 Enforcement entity viability ❌
#75 [TAG feedback] Handling additional types of ownership/controllership scenarios ❌
#87 Whether FPS transition should clear a site's data partitioned by other top-levels. ❌
#110 Machine-readable declaration for common ownership ❌
#123 Editorial: Consider renaming "equivalence map" ❌
#124 Editorial: Needs more detail on how FPS changes are computed ❌
#125 Describe client-side validation to prevent PSL mismatch ❌
#143 Introduction should reference requestStorageAccessFor ❌
#147 First-Party Sets User Education ❌
#156 Feature Request: JavaScript API for determining FPS status and enablement ❌