Re: [csswg-drafts] [css-fonts] @font-face src: url() format() keywords vs. strings ambiguous in spec (#6328)

Fonts 3 [only allowed strings](https://www.w3.org/TR/css-fonts-3/#src-desc) and restricted them to a given list, so the Gecko and Blink behavior is consistent with that. I'm not sure what the benefit is of also allowing keywords.

A format string which is unrecognized should result in that whole comma-delimited section being dropped, right?

```css
src: url(ideal-sans-serif.woff2) format("woff2"),
    url(ideal-sans-serif.zeb) format("zebra"),
  url(basic-sans-serif.ttf) format("opentype");
```
So a ua that does not support woff2 would skip over the zebra and download the opentype.

(side note, example in the spec is missing a comma)

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


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

Received on Wednesday, 2 June 2021 17:50:57 UTC