Looking at the proposal itself - it feels *slightly* weird to have context-specific @supports (I presume this *wouldn't* allow arbitrary property-support queries, but only font-based ones?). If I'm wrong about that and this would just be an ordinary @supports, with a supporting proposal to add the font-feature queries, then this is less weird. (If I'm right, naming it `@font-supports` or something would defuse my objection.) I don't have a *strong* opinion on whether this should be treated as a parse-time syntax, disappearing from the tree in the OM, or kept around like normal @supports is. Parse-time is definitely simpler overall, but I understand how it feels new and odd. Overall tho, I definitely support *something* like this over the growing weird microsyntax. The microsyntax was reasonable when it was just one thing, but it's getting out of hand. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6520#issuecomment-902994850 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Friday, 20 August 2021 22:48:13 UTC
This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:42 UTC