explainers-by-googlers / standardizing-cross-site-cookie-semantics
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
- Agenda and minutes of meetings of the Privacy Community Group☆98Updated last week
- ☆30Updated 2 years ago
- ☆123Updated 2 years ago
- ☆12Updated 2 years ago
- New proposals in the Privacy Community Group☆127Updated 2 years ago
- Cookies should take scheme into account, just like every other storage mechanism on the web.☆16Updated 4 years ago
- Privacy Sandbox Developer Enrollment and Attestations☆26Updated last month
- Aggregate Reporting API☆41Updated 4 years ago
- Client-Side Storage Partitioning☆79Updated last year
- Specification for the Client Hints infrastructure - privacy preserving proactive content negotiation☆63Updated 9 months ago
- This repository is to discuss proposals before they've been spun off into their on repository.☆20Updated 2 years ago
- A Modest Content Security Proposal☆40Updated 3 years ago
- Proposal to use a CONNECT proxy to obfuscate the user IP address for privacy-enhanced prefetching.☆36Updated 2 years ago
- A proposal for a cookie attribute to partition cross-site cookies by top-level site☆148Updated 6 months ago
- 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
- A proposal to partition :visited link history by top-level site and frame origin.☆19Updated 2 months ago
- Private Click Measurement☆198Updated 2 years ago
- ☆53Updated this week
- Secure Contexts, but with _more_ secureness!☆20Updated 10 months ago
- Explainer for proposed web platform Shared Storage API☆109Updated this week
- A Potential Privacy Model for the Web: Sharding Web Identity☆192Updated last year
- Proposal for a strong boundary between a page and its embedded content☆136Updated this week
- Proposal for HTTP headers related to the Storage Access API☆32Updated last month
- A proposed extension to the Storage Access API and discussion of how it may be integrated with First-Party Sets.☆24Updated last week
- Post-Spectre Web Development☆18Updated last year
- Navigation-based Tracking Mitigations☆38Updated last week
- Opaque Response Blocking (CORB++)☆35Updated 2 years ago
- User Interface Security and the Visibility API☆11Updated 4 years ago
- An API to allow developers transfer the ability to use restricted APIs to any target window in the frame tree.☆15Updated 8 months ago
- WebAppSec Content Security Policy☆217Updated last week