Re: [w3ctag/design-reviews] Anonymous iframes (#639)

I was going to reply in a few days:

>  Can this info be brought into the explainer to make that document more clear (including the linked user needs)?

Will be done by PR: https://github.com/camillelamy/explainers/pull/25

> Can you please progress the open issues including the one Tess pointed to

Tess pointed to https://github.com/camillelamy/explainers/issues/20, which is also addressed by PR https://github.com/camillelamy/explainers/pull/25.

>  Spec-wise where is this going? Is this headed to HTML?

I think mainly it is mainly HTML & fetch.

1. Adding the iframe's attribute and inheritance logic is going to happen in the HTML spec. Inheritance is similar to the sandbox attribute, modulo that this is only for iframe, it doesn't propagate to popups.

2. Some details: autofill, behavior of popup opened from anonymous iframe, etc are also going inside the HTML spec.

3. Getting an ephemeral storage partition is done by piggybacking on ongoing efforts. This is mostly about adding a `nonce` to the `network partition key` / `cookie partition key` / `storage partition key`, defined from: [Partition Network State](https://github.com/MattMenke2/Explainer---Partition-Network-State/blob/main/README.md), [Cookies Having Independent Partitioned State](https://github.com/WICG/CHIPS), [Client-Side Storage Partitioning](https://github.com/privacycg/storage-partitioning). This would touch HTML and fetch I believe.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/639#issuecomment-969161024