Re: [csswg-drafts] [css-images] Define what happens when all image-set options are invalid (#8266)

The CSS Working Group just discussed `[css-images] Define what happens when all image-set options are invalid`, and agreed to the following:

* `RESOLVED: if there are no valid options, render as an invalid image`

<details><summary>The full IRC log of that discussion</summary>
&lt;emeyer> emilio: If you specify an invalid type that the UA doesn’t understand, we don’t have a good answer for what happens<br>
&lt;emeyer> …Does the UA try to load and then discard?<br>
&lt;emeyer> …Tab put in the spec we render an invalid image<br>
&lt;emeyer> …The difference is that if the type function ends up invalid, like say it’s PNG in the CSS but then serve a JPEG, it’s a problem<br>
&lt;emeyer> …I think what Tab put in the spec is fine<br>
&lt;emeyer> astearns: Proposed resolution is to accept what’s been added to the spec?<br>
&lt;emeyer> TabAtkins: More specifically, if there are no valid options, it rendered as an invalid image<br>
&lt;fantasai> +1<br>
&lt;emeyer> astearns: Objections?<br>
&lt;emeyer> RESOLVED: if there are no valid options, render as an invalid image<br>
</details>


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


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

Received on Wednesday, 19 April 2023 16:34:22 UTC