From f9df872f63b62a70352fb123493a408d67d64200 Mon Sep 17 00:00:00 2001 From: Viviana Monsalve Date: Tue, 23 Aug 2022 23:13:56 -0500 Subject: [PATCH] Adding the default fallback requirement --- README.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index ebc1f1b82..6047534a4 100644 --- a/README.md +++ b/README.md @@ -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. +
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`