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

Relevant issue for an `if-elsif-else` block is https://github.com/w3c/csswg-drafts/issues/112

I agree that we need a syntax where: 

- exactly one branch is chosen (finding a winning one means you don't evaluate the rest)
- the logical tests for each branch can combine multiple boolean tests

Note that the existing, ugly, jammed-into-format syntax already has those properties; and I don't want to see it adopted anyway just for expediency because we take too long to add an `if-elsif-else` construct. I also don't want us to adopt a solution "for now" that has the multiple download and fallback problems that @jfkthame has explained so well.

> My only remaining thought is general distaste for using different mechanisms to select truetype/opentype vs COLR/sbix.

We will need to keep `format` for legacy reasons but nothing prevents our adding a format test to the new syntax along with the font technology tests. Although the spec already requires treating truetype and opentype as synonyms so `format` is mainly testing for new compression/deployment wrappers (woff, woff2, IFT, etc)

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


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

Received on Wednesday, 15 September 2021 11:56:13 UTC