-
Notifications
You must be signed in to change notification settings - Fork 77
Issues: WICG/first-party-sets
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Why depend on a 3rd party that a domain owner has no control over?
#180
opened Sep 27, 2023 by
dopry
FPS - How does enterprises control their first party sets which are internal?
#160
opened Jun 21, 2023 by
jagadeeshaby
Feature Request: JavaScript API for determining FPS status and enablement
#156
opened May 24, 2023 by
mikefleming
Changes to a domain's first-party-set.json after github submission
#151
opened Apr 26, 2023 by
brownwolf1355
Rename the required .well-known/first-party-set to include a .json extension
#149
opened Apr 25, 2023 by
sjledoux
Introduction should reference requestStorageAccessFor
editorial
#143
opened Apr 7, 2023 by
miketaylr
Clarification on subsets, specifically "associated" subsets
#139
opened Mar 3, 2023 by
Jack-Pritchard
Alternative to centralized GitHub repository for submission of First-Party Sets (FPS)
future
#128
opened Jan 18, 2023 by
brownwolf1355
Editorial: Needs more detail on how FPS changes are computed
editorial
#124
opened Dec 12, 2022 by
johannhof
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.