You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Upstream Document-Isolation-Policy to HTML and Fetch #8
Hi @camillelamy - with WebKit's portability concerns now resolved, it seems like upstreaming is the main thing standing between DIP and broad support. I'd love to help get this moving however I can. For reference, we use DIP in WordPress to drive the new client-side media feature.
I tried proposing DIP for Interop in web-platform-tests/interop#1332 and was informed upstreaming into HTML and Fetch was the appropriate next step.
Claude gathered up the current state of things, summary below:
The spec is already written as monkey-patches over HTML (policy containers, browsing context groups, agent clusters, the headers) and Fetch (CORP checks, HTTP-network-or-cache fetch), so the upstream work looks like paired PRs to whatwg/html and whatwg/fetch, similar to how COEP credentialless landed via whatwg/html#6638 and whatwg/fetch#1229.
Open questions:
Is Google planning to upstream this, and is there a rough timeline?
Would a tracking issue on whatwg/html be helpful now, to get the upstreaming discussion started there?
One more item that might be worth covering in the spec or tests: WordPress found that when only some same-origin pages send DIP, those pages end up in different agent clusters, which broke same-origin iframe access in the admin. See WordPress/wordpress-develop#11298. The current tests don't appear to cover that partial-deployment case.
Help I can offer: opening the whatwg tracking issues, filing the WebKit bug, writing WPT tests for the partial-deployment case, and adding web-features and MDN entries. Happy to take on whatever is most useful!
Activity
tommygaessler commentedon Sep 28, 2026
Thank you @adamsilverstein, glad to see this moving and happy to continue helping as well!
In July I encouraged Mozilla to choose a position and had Zoom submit to Apple via Feedback Assistant
FB23753562.Let me know what else I can do.
adamsilverstein commentedon Sep 29, 2026
Related: I opened a WebKit enhancement bug report: https://bugs.webkit.org/show_bug.cgi?id=325516