Re: [csswg-drafts] [mediaqueries] Spec has conflicting info on whether or not `<media-query-list>` allows trailing commas (#11254)

Ah yes, this seems to be a regression introduced in 6ab5888 (related: #8834). It is not present in the last published version of the spec, linked in your initial comment.

This algo is currently only used to parse a list of media queries, of selectors in `:is()`/`:where()`, and font sources in `@font-face/src`. The current version of Chrome and Firefox accept a trailing comma in all these places.

Related tests:

  - [`<media-query-list>`](https://github.com/web-platform-tests/wpt/blob/c88567a38512d333feb4b1c29106c7f0997ef1d8/css/mediaqueries/match-media-parsing.html)
  - [`<:is()>`/`<:where()>`](https://github.com/web-platform-tests/wpt/blob/c88567a38512d333feb4b1c29106c7f0997ef1d8/css/selectors/parsing/parse-is-where.html) (missing)
  - [`@font-face/src`](https://github.com/web-platform-tests/wpt/blob/master/css/css-fonts/parsing/font-face-src-list.html) (missing)

Simple fix:

```diff
- 2. [=Discard a token=] from |input|.
  2. If the current input code point is <comma-token>,
     repeat step 1.
```

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


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

Received on Thursday, 21 November 2024 13:15:44 UTC