- From: Jason Pamental via GitHub <sysbot+gh@w3.org>
- Date: Sun, 08 Oct 2017 17:33:01 +0000
- To: public-css-archive@w3.org
Seems like this discussion stalled. Has it moved elsewhere?
If we want to be able to define 'keyword norms' in the `@font-face` declaration, it seems like this syntax makes a lot of sense:
```
@font-face {
font-family: Hamstervar;
src: url("Hamstervar-VF.ttf");
font-stretch: normal;
font-weight: normal,
font-variation-settings: "wdth" 85, "wght" 327;
}
@font-face {
font-family: Hamstervar;
src: url("Hamstervar-VF.ttf");
font-weight: bold,
font-variation-settings: "wght" 572;
}
@font-face {
font-family: Hamstervar;
src: url("Hamstervar-VF.ttf");
font-stretch: expanded;
font-weight: bold,
font-variation-settings: "wdth" 112, "wght" 572;
}
```
This would allow us to define what the default rendering of `font-family: Hamstervar` would look like, just as it would then allow us to define `font-weight bold` or `font-stretch: expanded; font-weight: bold`
I'd certainly like to see this more clearly defined so we know what we're working towards (and can then explain/teach it in our talks and workshops!)
--
GitHub Notification of comment by jpamental
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1289#issuecomment-335023461 using your GitHub account
Received on Sunday, 8 October 2017 17:32:49 UTC