Re: [w3c/manifest] Define how the manifest is fetched (#481)

There are three entities that are 1:1:1 that you should know about: realm, global object, and environment settings object. Roughly, the global object is the thing JS developers see; the realm is the stuff the JavaScript spec uses to track extra data about the global environment; and the environment settings object is the stuff web platform specs use to track extra data about the global environment.

When doing a request, it's important to know what realm/global/settings object it came from. This is embodied in the concept of a request client, which is an environment settings object.

I think you should probably just set the client to the element's [relevant settings object](https://html.spec.whatwg.org/multipage/webappapis.html#relevant-settings-object). However, I just checked https://html.spec.whatwg.org/multipage/semantics.html#concept-link-obtain, and it uses the more complicated formalism of "the link element's node document's Window object's environment settings object." That seems weird to me... @annevk, any thoughts on why it does that?

Also it seems like this spec is duplicating https://html.spec.whatwg.org/multipage/semantics.html#concept-link-obtain (just with different CORS semantics), which is a bit sad?

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/481#issuecomment-237476944