Contact emails
j...@chromium.org
Specification
https://drafts.csswg.org/css-values-5/#request-url-modifiers
Summary
CSS url() functions accept optional request modifiers after the quoted URL string: cross-origin(), integrity(), and referrer-policy(). These modifiers control the fetch behavior of the referenced resource directly from CSS, without requiring changes to HTML markup or JavaScript. For example, background-image: url("image.png" cross-origin(anonymous)) fetches the image using CORS anonymous mode. This gives authors fine-grained control over cross-origin access, subresource integrity, and referrer policy for CSS-loaded resources including images, fonts, SVG references, and imported stylesheets.
Blink component
Blink>CSS
Web Feature ID
url-cross-origin, url-referrer-policy, url-integrity
Motivation
Web developers currently have no way to control fetch parameters for CSS-loaded resources. CSS URL request modifiers close this gap by allowing fetch parameters to be specified inline in any url() value, bringing CSS resource loading to parity with HTML resource loading.
Initial public proposal
No information provided
TAG review
No information provided
TAG review status
Not applicable
Goals for experimentation
None
Risks
Debuggability
No information provided
Will this feature be supported on all six Blink platforms
(Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
Yes
Yes
https://wpt.fyi/results/css/css-values/urls
Flag name on about://flags
No information provided
Finch feature name
CSSURLRequestModifiers
Rollout plan
Will ship enabled for all users
Requires code in //chrome?
False
Tracking bug
https://issues.chromium.org/issues/435625756
Estimated milestones
| Shipping on desktop | 149 |
| Shipping on Android | 149 |
| Shipping on WebView | 149 |
Anticipated spec changes
Open questions about a feature may be a source of future web compat or
interop issues. Please list open issues (e.g. links to known github
issues in the project for the feature specification) whose resolution
may introduce web compat/interop risk (e.g., changing to naming or
structure of the API in a non-backward-compatible way).
No information provided
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5111997147512832?gate=6585091942907904
Links to previous Intent discussions
Intent to Prototype:
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/69d421df.050a0220.2539d3.00af.GAE%40google.com