Add cross-site ancestor flag to environment. (privacycg/storage-parti…

[wanderview]

…tioning#25)

• At least two implementers are interested (and none opposed):
  • …
  • …
• Tests are written and can be reviewed and commented upon at:
  • …
• Implementation bugs are filed:
  • Chrome: …
  • Firefox: …
  • Safari: …
  • Deno (only for timers, structured clone, base64 utils, channel messaging, module resolution, web workers, and web storage): …
  • Node.js (only for timers, structured clone, base64 utils, channel messaging, and module resolution): …

(See WHATWG Working Mode: Changes for more details.)

---

/browsers.html ( diff )
/browsing-the-web.html ( diff )
/webappapis.html ( diff )
/window-object.html ( diff )
/workers.html ( diff )

[wanderview]

This is a speculative PR for privacycg/storage-partitioning#25. It lays the groundwork for adding the bit to the storage key in a separate PR. Also, if this lands we need a follow-up to set the environment bit when a service worker is created.

[johannhof]

I realized that this is probably what we need for #9729, @annevk let's try to figure out what's missing here

[bvandersloot-mozilla]

I built on top of this for whatwg/fetch#1807 to help spec SameSite=Strict in Fetch.

[johannhof]

@annevk with the layering work progressing, this looks to be a blocker for Ben's PR in whatwg/fetch#1807.

Could you please review this as HTML editor and add some thoughts on what's needed to get this over the finish line? :)

Thanks!

[annevk]

Adding this to all environments is probably a reasonable step. It needs to be rebased for review as I'm not really sure how much all of this changed with navigables and such.

[domenic]

I'm curious how this relates to #8014 and #8027.

[johannhof]

@bvandersloot-mozilla just to confirm - you said you'd pick this up as well, right? (Happy to provide help from our side if you need any :)

[bvandersloot-mozilla]

Yep: it is in the autotag from March 14: #11133