html no longer defines "referrer source"

[mkruisselbrink]

@annevk removed the definition of "referrer source" in whatwg/html@7c5555a , but this spec still links to that (in Run Service Worker and the importScripts definition). This should somehow be fixed.

[domenic]

It looks to me like this is solvable by removing the reference to "referrer source" in the definition of the settings object (in Run Service Worker), then in importScripts saying "with referrer set to settings object's API base URL."

[annevk]

If referrer matches the client you passes to Fetch, you don't have to set it at all. Referrer is never the base URL by the way (unless it happens to match the URL of the resource).

[jakearchibald]

Pre F2F notes: Does @domenic's proposal work here?

[domenic]

Hmm, now that I know more about this, probably not. Setting the referrer from a settings object is in general tricky; see https://w3c.github.io/webappsec-referrer-policy/#determine-requests-referrer.

[jungkees]

F2F: Change SW to use referrer policy language.

[jungkees]

@annevk, @domenic, here's my plan (Correct me if I'm wrong):

Remove the reference to "referrer source" in the definition of the settings object (in Run Service Worker) and add a reference to "referrer policy" instead that returns "worker global scope's referrer policy". Worker global scope's referrer policy is set when fetching the script in Update algorithm as other workers do in run a worker: "Set worker global scope's referrer policy to the result of parsing the Referrer-Policy header of response."

[annevk]

Sounds reasonable.

[domenic]

Sounds exactly right, thanks!