Re: [csswg-drafts] [css-fonts-4][css-nesting] Nesting of @supports inside @font-face (#6520)

In [this branch](https://github.com/drott/csswg-drafts/commit/7a63d1c44c98c4971d2922dce8094dcb48d44b7a) I drafted an edit to [css-conditional-4](https://drafts.csswg.org/css-conditional-4/#at-supports-ext), carrying over the syntax from [fonts-4's - Parsing the source descriptor](https://drafts.csswg.org/css-fonts/#font-face-src-parsing), an excerpt from that draft (feel free to comment on the [commit](https://github.com/drott/csswg-drafts/commit/7a63d1c44c98c4971d2922dce8094dcb48d44b7a) directly as well):

```
<supports-feature> = <supports-selector-fn> | <supports-font-technology-fn> | <supports-decl>
<supports-selector-fn> = selector( <complex-selector> )
<supports-font-technology-fn> = font-technology ( <font-technology> )
<font-technology> = [ features( <font-feature-technology> ) | variations
                    | color( <color-font-technology> ) | palettes | incremental ]
<font-feature-technology> = [ opentype | aat | graphite]
<color-font-technology> = [ COLRv0 | COLRv1 | SVG | sbix | CBDT ]
```

Considerations:

* I did not add a repetition operator _#_ after `<font-technology>` in the `<supports-font-technology-fn>` rule as required combinations of technologies can be expressed through `and` and `or` of the `@supports` syntax, which I consider an improvement over the syntax in the fonts spec.

I'd be very happy if in tomorrow's meeting we could attempt to resolve towards a direction of the syntax along those lines (feedback very welcome), in addition to the general aim to resolve adding the criteria to the `@supports` rule.


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


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

Received on Tuesday, 24 August 2021 12:55:39 UTC