Re: [csswg-drafts] [css-images] image-set: should we serialize options with unsupported type? (#8495)

Right, that probably wasn't clear.

If I have something like this:

```CSS
image-set(url("img.png") type("image/png"), url("img.unsupported"), type("image/unsupported"))
```

Which should it serialize to?

```
'image-set(url("img.png") 1dppx type("image/png"), url("img.unsupported") 1dppx type("image/unsupported"))'
'image-set(url("img.png") 1dppx type("image/png"))'
```

My point about omitting the unsupported type was that the image that is chosen by the engine will be the same in either case.

-- 
GitHub Notification of comment by rreno
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8495#issuecomment-1444609682 using your GitHub account


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

Received on Friday, 24 February 2023 22:43:52 UTC