Re: [csswg-drafts] [css-values] Define crossorigin, preload and async URL modifiers (#1603)

The CSS Working Group just discussed `[css-values] Define crossorigin, preload and async URL modifiers`, and agreed to the following:

* `RESOLVED: Leave the values in Level 5`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> github: https://github.com/w3c/csswg-drafts/issues/1603<br>
&lt;emeyer> TabAtkins: We agreed to add additional URL modifiers<br>
&lt;emeyer> …ALl the things you can do with Fetch or with HTML links<br>
&lt;emeyer> …We never defined them, put them off to another level<br>
&lt;emeyer> …Gnome went ahead and defined three of them [missed the three]<br>
&lt;emilio> q+<br>
&lt;emeyer> …THe mechanics are reasonable and match up with what you’d do in HTML<br>
&lt;astearns> s/Gnome/Noam/<br>
&lt;emeyer> …Does anyone have any objections to these, and are they fine for Values 4 or do they need to wait for Values 5?<br>
&lt;astearns> ack emilio<br>
&lt;emeyer> emilio: What do preload and async do?<br>
&lt;emeyer> …Preloading in the context of CSS values doesn’t make a lot of sense ot me<br>
&lt;emeyer> TabAtkins: Noam added crossorigin, integrity, and referrer<br>
&lt;emeyer> s/ot/to/<br>
&lt;TabAtkins> https://w3c.github.io/csswg-drafts/css-values-5/#request-url-modifiers<br>
&lt;emeyer> emilio: I’m curious about the integrity string, is that a function?<br>
&lt;emeyer> TabAtkins: Yep, takes a string that is the hash<br>
&lt;emeyer> emilio: Seems fine to me<br>
&lt;astearns> ack fantasai<br>
&lt;emeyer> fantasai: I’d prefer to leave them in Level 5 because they’re already drafted there<br>
&lt;emeyer> …I’d also like to get L4 to CR by closing out issues<br>
&lt;emeyer> astearns: Anyone want to argue for L4?<br>
&lt;emilio> q+<br>
&lt;emeyer> TabAtkins: L4 holds some things that aren’t implemented, so we should kick those out; these are stable and appropriate<br>
&lt;emeyer> …I don]t want to kick these out for arbitrary reasons<br>
&lt;astearns> ack emilio<br>
&lt;emeyer> emilio: I just realized we force crossorigin to be anonymous for CSS already<br>
&lt;emeyer> …We need to define whether you can override it; I don’t think you should be able to<br>
&lt;tantek> +1 to consistent methodology for level 4 vs 5, ok with dropping things from L4 that have zero implementations. probably a good move before CR<br>
&lt;emeyer> …Masks, for example, require anonymous crossorigin loads<br>
&lt;emeyer> …So we should define that<br>
&lt;emeyer> TabAtkins: I don’t think they’re defined in a way that hooks into these, so we need to review that<br>
&lt;emeyer> astearns: We should resolve to leave these in L5; any objections?<br>
&lt;emeyer> RESOLVED: Leave the values in Level 5<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1603#issuecomment-1505619189 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 12 April 2023 17:01:58 UTC