Would would it take to implement this? Is it anything more than reading the attribute at the various places a preload header can be defined and setting the right flag on the request?
Does referrer policy impact resource reuse in ResourceFetcher?
Re #3: I think ideally it shouldn't just be <link rel="preload"> but also other fetches for external resources, namely <link rel="icon"> and <link rel="stylesheet">. But, yeah, it's basically a matter of setting the referrer policy on the request whenever an HTMLLinkElement creates a request.
One note is that HTMLPreloadScanner will have to pick up the referrer policy attribute when scanning link elements. I think that should just be a matter of setting |m_referrerPolicy| when parsing a referrerpolicy attribute on a link element, similar to what we already do for img elements: https://cs.chromium.org/chromium/src/third_party/WebKit/Source/core/html/parser/HTMLPreloadScanner.cpp?sq=package:chromium&rcl=1476127171&l=328
> Does referrer policy impact resource reuse in ResourceFetcher?
Nope, don't think so. It should only affect outgoing HTTP requests.
Comment 1 by est...@chromium.org
, Oct 6 2016