Editorial: make settings object's referrer policy a dfn#1718
Conversation
|
This appears to be out of date. The definition for referrer policy moved, but also you seem to have deleted the definition of a request's referrer policy, which we should keep... |
|
Re-reviewing this with an eye toward what it is actually trying to accomplish, I think it is probably a good idea, once rebased and disentangled from the other change. I wonder if we should do the same thing for module map and origin. |
|
I can change those too if you want. Somewhere Monday. |
|
Sure, if you're up for it, although I think there will be a lot of references to them (especially to origin) that need updating. Either together or in a separate patch is good. |
This allows Fetch and Referrer Policy to reference it directly. In addition, move the definition of referrer policy itself per changes in Fetch and Referrer Policy.
annevk
force-pushed
the
settings-object-referrer-policy
branch
from
f2ee3ac to
58197f4
Compare
|
This should be good now. I don't think I ever removed request's referrer policy btw, I just moved something similar to what a PR you created did since that had not landed at the time (and I included "The" and "concept" around it). |
A follow up to #1718 to let folks be more specific when talking about module maps and origins.
A follow up to whatwg#1718 to let folks be more specific when talking about module maps and origins.
2 participants
This allows Fetch and Referrer Policy to reference it directly. In
addition, move the definition of referrer policy itself per changes in
Fetch and Referrer Policy.