- From: Myles C. Maxfield via GitHub <sysbot+gh@w3.org>
- Date: Wed, 25 Aug 2021 18:48:29 +0000
- To: public-css-archive@w3.org
It was brought up on today's call that we already have the typo problem, but I think that typo problem and this typo problem are different enough that they're worth distinguishing between. If an author uses two font face blocks to create a family, their goal is to associate the fonts together and have them act as a single family. If the author makes a typo, the exact boundaries between the different faces in that family will be wrong, but they will still have achieved their general purpose - associate the fonts together and have them act as a single family. In the situation in https://github.com/w3c/csswg-drafts/issues/6520#issuecomment-905691885, their goal is _not_ to create a family; their goal is progressive enhancement on newer browsers. If they make a typo, they haven't achieved their general purpose; they've instead triggered a totally different kind of functionality, which can behave exactly the opposite of what they were intending to do in the first place. -- GitHub Notification of comment by litherum Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6520#issuecomment-905786305 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 25 August 2021 18:48:31 UTC