What is the relationship between type values and a Web request's destination concept?

[littledan]

The concept of a request's destination has names for different things where a request can originate from. These can be read from a Request object's destination property, or passed in from <link rel="preload"> in the as= attribute. Should this concept relate to the type: values somehow?

h/t to @slightlyoff for drawing this connection

[annevk]

Changing this value might make sense, but that would require specifying some hierarchy of privilege.

E.g., if you allow JavaScript, it can remain "script", if you only allow JSON, it can be "json". If you allow either, "script".

[bmeck]

Should this even be specified/mandated if other environments without that concept are being considered?

[littledan]

We will have to take care for layering. One possibility is for named to be in loose correspondence with each other, but without ES citing Web specs. Another possibility is that this is a correspondence that exists in HTML's interpretation of the type, and not JS's.

[littledan]

Ultimately, I think the strings in the type: attribute will be different from the set of request destinations. They may be related, but not 1:1. This is something to work through in the HTML integration, as it may have implications for what HTTP headers to send in the request, before Stage 3.