explainers-by-googlers / standardizing-cross-site-cookie-semantics
A proposal to standardize security semantics of cross-site cookies
☆17Updated 11 months ago
Related projects ⓘ
Alternatives and complementary repositories for standardizing-cross-site-cookie-semantics
- Agenda and minutes of meetings of the Privacy Community Group☆95Updated last month
- Client-Side Storage Partitioning☆71Updated last year
- Specification for the Client Hints infrastructure - privacy preserving proactive content negotiation☆61Updated 5 months ago
- New proposals in the Privacy Community Group☆124Updated 2 years ago
- Aggregate Reporting API☆41Updated 4 years ago
- ☆118Updated last year
- ☆11Updated 2 years ago
- ☆49Updated this week
- Navigation-based Tracking Mitigations☆35Updated 3 weeks ago
- Explainer for proposed web platform Shared Storage API☆95Updated last week
- Cookies should take scheme into account, just like every other storage mechanism on the web.☆16Updated 4 years ago
- Proposal for a strong boundary between a page and its embedded content☆130Updated last week
- This is both a terrible and wonderful idea.☆10Updated 5 years ago
- Secure Contexts, but with _more_ secureness!☆20Updated 6 months ago
- Private Click Measurement☆198Updated 2 years ago
- Proposal to use a CONNECT proxy to obfuscate the user IP address for privacy-enhanced prefetching.☆35Updated 2 years ago
- An API to allow developers transfer the ability to use restricted APIs to any target window in the frame tree.☆14Updated 4 months ago
- A proposal for a cookie attribute to partition cross-site cookies by top-level site☆131Updated 2 months ago
- A proposed extension to the Storage Access API and discussion of how it may be integrated with First-Party Sets.☆21Updated 2 weeks ago
- Repo to track PING initiated issues on other standards documents.☆12Updated 3 weeks ago
- A Modest Content Security Proposal☆40Updated 3 years ago
- ☆30Updated 2 years ago
- User Interface Security and the Visibility API☆11Updated 3 years 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 last year
- A target privacy threat model for the Web☆23Updated 3 years ago
- WebAppSec Credential Management☆50Updated 2 months ago
- Privacy Sandbox Developer Enrollment and Attestations☆22Updated 4 months ago
- A Potential Privacy Model for the Web: Sharding Web Identity☆188Updated 10 months ago
- This repository is to discuss proposals before they've been spun off into their on repository.☆20Updated 2 years ago
- Explainer for proposed web platform API☆45Updated this week