explainers-by-googlers / standardizing-cross-site-cookie-semanticsLinks
A proposal to standardize security semantics of cross-site cookies
☆17Updated last year
Alternatives and similar repositories for standardizing-cross-site-cookie-semantics
Users that are interested in standardizing-cross-site-cookie-semantics are comparing it to the libraries listed below
Sorting:
- Agenda and minutes of meetings of the Privacy Community Group☆99Updated this week
- Cookies should take scheme into account, just like every other storage mechanism on the web.☆16Updated 5 years ago
- Specification for the Client Hints infrastructure - privacy preserving proactive content negotiation☆63Updated 11 months ago
- New proposals in the Privacy Community Group☆128Updated 2 years ago
- ☆124Updated 2 years ago
- Navigation-based Tracking Mitigations☆38Updated 2 months ago
- ☆12Updated 3 years ago
- Aggregate Reporting API☆42Updated 4 years ago
- A proposed extension to the Storage Access API and discussion of how it may be integrated with First-Party Sets.☆27Updated 2 months ago
- Explainer for proposed web platform Shared Storage API☆112Updated last month
- Client-Side Storage Partitioning☆82Updated 2 years ago
- ☆30Updated 2 years ago
- The Storage Access API☆235Updated last month
- A proposal for a cookie attribute to partition cross-site cookies by top-level site☆152Updated last month
- What if developers could opt-into better default behaviors en masse, forcing them to pick and choose the legacy risks they want to enable…☆19Updated 2 years ago
- Private Click Measurement☆201Updated 3 years ago
- Proposal for a strong boundary between a page and its embedded content☆140Updated last month
- Privacy Sandbox Developer Enrollment and Attestations☆29Updated 3 months ago
- ☆55Updated 2 months ago
- Proposal for HTTP headers related to the Storage Access API☆38Updated last month
- Minutes of all TAG Meetings and Calls☆60Updated this week
- ☆24Updated 11 months ago
- Secure Contexts, but with _more_ secureness!☆20Updated last year
- An API to allow developers transfer the ability to use restricted APIs to any target window in the frame tree.☆16Updated 10 months ago
- Proposal to use a CONNECT proxy to obfuscate the user IP address for privacy-enhanced prefetching.☆37Updated 3 years ago
- A Potential Privacy Model for the Web: Sharding Web Identity☆197Updated last year
- ☆51Updated 9 months ago
- Agenda/Minutes of Anti-Fraud Community Group meetings.☆19Updated last week
- A place to raise issues with the WHATWG Steering Group☆70Updated last week
- This repository is to discuss proposals before they've been spun off into their on repository.☆22Updated 2 years ago