Navigation API: Navigation History Entry url getter - bug in spec or tests? #11941
Description
What is the issue with the HTML Standard?
The url getter steps for Navigation History Entry, step 4 says the following:
- If she's document does not equal document, and she's document state's request referrer policy is "no-referrer" or "origin", then return null.
It's explicitly mentioned here, and provided links for, that we're referring to the policy with which the document was fetched - not the the policy that the document then itself uses to fetch resources with.
However, there are explicit web platform tests named no-referrer-dynamic-url-censored that does the following:
- insert a meta tag that changes referrer policy for the document
- then expects this to affect the url getter steps
However, using <meta> should only change the fetches made by the document, not by the document itself. The specification makes the distinction between these two by having a "request referrer policy" and a "history policy container" (which contains the document's referrer policy). A note can be read about it:
The request referrer policy is distinct from the history policy container's referrer policy. The former is used for fetches of this document, whereas the latter controls fetches by this document.
I'm filing the issue here (and will file one for WPT) not in hopes necessarily to have this change in the standard, because I honestly do not see this being useful and just adding unnecessary complexity to an already complex suite of features (the Navigation API). I'm mainly filing this, so that the issues for the spec as well as WPT can track each other.
Cc @zcorpan @farre I'll leave it to you to cc additional people you think are relevant.