- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Aug 2023 16:31:08 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `tech() validation`, and agreed to the following: * `RESOLVED: Make edits outlined by Chris` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: tech() validation<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/8793<br> <fantasai> jfkthame: Current spec text is a bit confusing<br> <fantasai> jfkthame: question is, if the font technology or font format that is declared for a font resource is not supported, how does this get processed<br> <fantasai> jfkthame: one part says if not supported, then that source is dropped from list of available sources<br> <fantasai> jfkthame: if no sources left, that's a parse error<br> <fantasai> jfkthame: another part of spec says that the format and tech are evaluated at the time of deciding what resources to load<br> <fantasai> jfkthame: so skip if don't support them<br> <fantasai> jfkthame: but it's not a CSS parse error<br> <fantasai> jfkthame: general agreement among those in discussion<br> <fantasai> jfkthame: is that unsupported tech or formats shouldn't be a parse error, it's still valid, you just don't fetch that resource<br> <fantasai> jfkthame: currently that's not what a strict reading of the spec says<br> <fantasai> jfkthame: if we agree it's not a parse error, then we need to fix the spec<br> <TabAtkins> +1, spec is simply written a little wrong, easy fix<br> <fantasai> +1<br> <vitorroriz> (I'm not on the call due to a meeting but +1)<br> <fantasai> astearns: proposed resolution is to remove bit about it being a parse error?<br> <fantasai> jfkthame: yes, looking at Chris's comment from July 11th<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/8793#issuecomment-1631228711<br> <fantasai> jfkthame: Proposed edits in that comment makes sense to me<br> <fantasai> RESOLVED: Make edits outlined by Chris<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8793#issuecomment-1680923925 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 August 2023 16:31:11 UTC