Howdy, Stranger!
Categories
- All Categories
- 39 Introductions
- 3.6K Typeface Design
- 764 Font Technology
- 1K Technique and Theory
- 589 Type Business
- 435 Type Design Critiques
- 526 Type Design Software
- 30 Punchcutting
- 132 Lettering and Calligraphy
- 79 Technique and Theory
- 53 Lettering Critiques
- 461 Typography
- 289 History of Typography
- 111 Education
- 61 Resources
- 479 Announcements
- 74 Events
- 104 Job Postings
- 147 Type Releases
- 153 Miscellaneous News
- 259 About TypeDrawers
- 52 TypeDrawers Announcements
- 109 Suggestions and Bug Reports
Options
[OTVar] CSS draft spec for variations support in web browsers
Laurence Penney
Posts: 49
I encourage anyone interested in Variations Fonts to read the draft CSS spec carefully:
https://drafts.csswg.org/css-fonts-4/#low-level-font-variation-settings-control-the-font-variation-settings-property
I was surprised to read this: “Axis values not present in the font, or axis values greater or less than the range supported by the font, are ignored and therefore have no effect…”
I would have thought it makes more sense to clamp values outside the axis’s range to either its max or its min, as recorded in the fvar table, rather than its default. Furthermore, there does not seem to be a way to obtain the max and min values — something that seems to me quite a desirable capability, whether or not there are instances to access them. Would it make sense to allow special values of max, min and default in font-variation-settings? For example:
font-variation-settings: 'wght' default, 'wdth' min;
Note: Webkit Nightly supports font-variation-settings but I have found it unpredictable when using values just within the extremes.
https://drafts.csswg.org/css-fonts-4/#low-level-font-variation-settings-control-the-font-variation-settings-property
I was surprised to read this: “Axis values not present in the font, or axis values greater or less than the range supported by the font, are ignored and therefore have no effect…”
I would have thought it makes more sense to clamp values outside the axis’s range to either its max or its min, as recorded in the fvar table, rather than its default. Furthermore, there does not seem to be a way to obtain the max and min values — something that seems to me quite a desirable capability, whether or not there are instances to access them. Would it make sense to allow special values of max, min and default in font-variation-settings? For example:
font-variation-settings: 'wght' default, 'wdth' min;
Note: Webkit Nightly supports font-variation-settings but I have found it unpredictable when using values just within the extremes.
Tagged:
1
Comments
The OT 1.8 spec says that an application (or whatever platform layer is doing interpolation) must clamp the requested user values to the axis min/max values defined in the 'fvar' table. Search for the first instance of "clamp" in this page:
https://www.microsoft.com/typography/otspec/otvaroverview.htm
Now, in principle, you could view CSS as a higher-level protocol that enforces different requirements. The OT spec doesn't prevent that; the higher-level protocol wouldn't conform to the OT 1.8 guidance for processing variation instance coordinates, but that doesn't necessarily imply that anyone will care.
But if people do care about what CSS does, they should open issues or comment on issues in the GitHub rep that the CSS WG uses for their process. I have opened an issue for this item (specifically, clamping vs. ignore; I haven't mentioned support for "min" and "max" values):
https://github.com/w3c/csswg-drafts/issues/647
Being able to ask for max, min, absolute percentage, and relative percentage all seem useful.
Dave, I like the idea of a percentage along an axis, so 0% gets its min, and 100% gets its max. Could you clarify what you mean by relative and absolute percentage?