Ready for Developer Testing: Modulepreload Referrer Header Fix

[Chromestatus]

Contact emails

hjanu...@gmail.com

Explainer

None

Specification

https://html.spec.whatwg.org/multipage/webappapis.html#concept-script-fetch-options-referrer-policy

Summary

Fixes modulepreload to properly send referrer headers by using ClientReferrerString() instead of NoReferrer(). This aligns Chrome with the HTML specification which requires using the client's referrer for module fetches. Includes WPT test verifying both dynamic imports and modulepreload correctly send referrer headers.

Blink component

Blink>Loader>Preload

TAG review

None

TAG review status

Not applicable

Risks

Interoperability and Compatibility

None

Gecko: Positive

WebKit: Positive

Web developers: No signals

Other signals:

WebView application risks

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?

None

Goals for experimentation

Ongoing technical constraints

None

Debuggability

None

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

Yes

minor change, with platform independance

Is this feature fully tested by web-platform-tests?

Yes

the CL comes with a WPT that verifies the behaviour, running the WPT out of CL verify's that it is currently failing without the code change

Flag name on about://flags

None

Finch feature name

None

Non-finch justification

None

Requires code in //chrome?

False

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5117573938806784

Links to previous Intent discussions

Intent to Prototype: http://crrev.com/c/6509110

This intent message was generated by Chrome Platform Status.

[Mike Taylor]

I suspect this is supposed to be an I2S (per https://chromium-review.googlesource.com/c/chromium/src/+/6509110/comments/da10e968_f515270f), but if "Ready for Developer Testing" is the correct stage - a feature flag for devs to flip and test would be useful. 

Could you clarify? Thanks

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/681d293e.170a0220.17d3dd.0097.GAE%40google.com.

[Helmut Januschka]

sorry for the confusion, it was my first time using https://www.chromestatus.com/features

lets close this one, i just re-sent the feature with i2s