- From: Dominic Farolino via GitHub <sysbot+gh@w3.org>
- Date: Sun, 30 Apr 2023 15:26:18 +0000
- To: public-css-archive@w3.org
Is there a concrete action item for this issue at this point? It seems that:
1. @noamr's PR is merged
2. We agree that resources in non-inline CSS sheets should use the CSS sheet's URL as the referrer
- Safari apparently doesn't do this?
4. CORS here shouldn't impact whether the `Referer` is sent (I believe)
The compat risk raised in the OP was (correct me if I'm wrong) that a font preload's referrer will be the Document's URL, while the font's _actual fetch_'s referrer will be a style sheet URL, yet reuse the different-referrer preload response. I guess this only matters when servers send `Vary: Referer`, which I don't think influences the preload cache. But per https://github.com/w3c/csswg-drafts/issues/6775#issuecomment-954517516 it sounds like this is documented now.
Can we just file a bug against Safari for (2) above and close this, or is there something specific that can still emerge from this?
--
GitHub Notification of comment by domfarolino
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6775#issuecomment-1529053696 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 30 April 2023 15:26:20 UTC