W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2016

[csswg-drafts] [css-values][all] Define all URL usages in terms of Fetch

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Mon, 03 Oct 2016 22:22:56 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-180762271-1475533372-sysbot+gh@w3.org>
tabatkins has just created a new issue for 
https://github.com/w3c/csswg-drafts:

== [css-values][all] Define all URL usages in terms of Fetch ==
The platform has settled on using the Fetch model to define fetching. 
CSS currently hand-waves a bunch of this, and as a result there are 
some browser-compat issues with corner cases, like what referrer to 
use in various situations.

[WebAppSec defines some of this behavior *for* 
us](https://github.com/w3c/webappsec-referrer-policy/issues/5#issuecomment-249556892)
 ([and 
here](https://github.com/w3c/webappsec-referrer-policy/pull/34/files#diff-117d6498d2aa8019cc0abf5eeb87a9fa)),
 which we should move into a CSS spec.

(This is mostly a tracking bug to remind me to do this, and track 
links to useful resources. If anyone else clueful would like to help, 
feel free.)

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/562 using your GitHub 
account
Received on Monday, 3 October 2016 22:23:04 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:04 UTC