explainers-by-googlers / Partitioning-visited-links-history
A proposal to partition :visited link history by top-level site and frame origin.
☆19Updated 2 months ago
Alternatives and similar repositories for Partitioning-visited-links-history:
Users that are interested in Partitioning-visited-links-history are comparing it to the libraries listed below
- `document.domain` intentionally weakens the only security boundary we have. Perhaps we can dump it?☆16Updated last year
- Evil Traps for Firefox☆15Updated 3 months ago
- Opaque Response Blocking (CORB++)☆35Updated 2 years ago
- Cookies should take scheme into account, just like every other storage mechanism on the web.☆16Updated 4 years ago
- TC39 proposal for mitigating prototype pollution☆46Updated last year
- A proposal to standardize security semantics of cross-site cookies☆17Updated last year
- A Modest Content Security Proposal☆40Updated 3 years ago
- Explainers from Mozilla contributors☆19Updated 2 weeks ago
- This is both a terrible and wonderful idea.☆11Updated 5 years ago
- Client-Side Storage Partitioning☆79Updated last year
- The Paper Artifact Availability☆20Updated 2 years ago
- User Interface Security and the Visibility API☆11Updated 4 years ago
- What is browser fingerprinting and how should specification authors address it.☆60Updated this week
- Fetch Metadata☆74Updated last month
- rewrite constructor arguments, call DOMPurify, profit☆67Updated 5 months ago
- Secure Contexts, but with _more_ secureness!☆20Updated 10 months ago
- ☆59Updated last month
- Explainer for Schemeful Same-Site☆15Updated 4 years ago
- Signature-based Resource Loading Restrictions☆34Updated 3 weeks ago
- Agenda and minutes of meetings of the Privacy Community Group☆98Updated last week
- A target privacy threat model for the Web☆24Updated 3 years ago
- Repo to track PING initiated issues on other standards documents.☆12Updated 4 months ago
- Find XS-Leaks in the browser by diffing DOM-Graphs in two states☆14Updated 2 months ago
- Specifications for Privacy Proxy Implementations☆30Updated this week
- Source Code Transparency☆11Updated last year
- New proposals in the Privacy Community Group☆127Updated 2 years ago
- Composite GitHub CI Action containing the minimal viable security lint for brave repositories☆18Updated this week
- `COEP: x-bikeshed-credentialless-unless-cors`☆28Updated 2 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 2 years ago
- Test domain for tracking protection☆19Updated 2 years ago