jprdonnelly/fonts
1
0
Fork 0
mirror of synced 2025-12-19 17:48:10 -05:00
Code Issues Projects Releases Wiki Activity

Adding the default fallback requirement

Browse Source
This commit is contained in:
Viviana Monsalve
2022-08-23 23:13:56 -05:00
committed by GitHub
parent 3737cef61e
commit f9df872f63
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@@ -27,12 +27,13 @@ When the registry is updated here, a line like `axisregistry/axis_name.textproto
* `precision`
* Describes the specificity at which an axis position can be specified.
For example, `0` means values must be specified as whole numbers while `-1` means values can be as precise as one decimal place.
* `fallback` (repeated)
* `fallback`
* Instance positions along the axis, such as wght 100,200,300,400,500,600,700,800,900.
* A cross-product of fallback positions along all supported axes is created to support legacy browsers that lack variable font support.
For axes with CSS3 properties (such as [font-weight](https://drafts.csswg.org/css-fonts-3/#font-weight-prop)), the positions accessible
to CSS3 should be specified. For axes lacking CSS3 properties a legacy browser is limited to a single position and that position must
be at a fallback.
<br>In case an axis doesn't include predefined positions, it is mandatory to define at least one fallback position. It should be called `Default` and its value should correspond to the `default_value` position of the axis.
* `fallback_only`
* Describes whether to only use fallback values when presenting to users.
* `description`