You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oh. So the problem is that the css-fonts-4 spec fails to define the <absolute-type> type properly. It defines the construct as a value instead. That value links back to the definition of <absolute-type> in CSS2, which is incorrect as that version does not have xxx-large.
If there is a proper type definition in css-fonts-4, it will automatically override the definition in CSS2 in Webref. We'll still need a syntax patch, but that patch will then be for css-fonts-4, and not for CSS2.
I'll propose an update to css-fonts-4. I'd say it's fine to adjust the syntax patch to add xxx-large in the meantime, even if the patch needs to remain tied to the definition in CSS2 for the time being.
Spec was updated. And I was wrong: the syntax in css-fonts-4 can actually be extracted automatically, which means the syntax patch is no longer needed at all. I dropped it.
New syntax with xxx-large will be released once #1783 can be merged. I'm closing this issue as addressed.
Note: The spec encloses the syntax in square brackets, which aren't necessary when considering the syntax in isolation. This is not the only case where enclosing square brackets are used. We could try to normalize syntaxes in the curated data if there's a need for it. Sticking to what the spec defines in the meantime.
Activity
tidoust commentedon Jan 9, 2026
Oh. So the problem is that the
css-fonts-4spec fails to define the<absolute-type>type properly. It defines the construct as avalueinstead. That value links back to the definition of<absolute-type>inCSS2, which is incorrect as that version does not havexxx-large.If there is a proper type definition in
css-fonts-4, it will automatically override the definition inCSS2in Webref. We'll still need a syntax patch, but that patch will then be forcss-fonts-4, and not forCSS2.I'll propose an update to
css-fonts-4. I'd say it's fine to adjust the syntax patch to addxxx-largein the meantime, even if the patch needs to remain tied to the definition inCSS2for the time being.[css-fonts-4] Create proper types for `<absolute-size>` and `<relativ…
[css-fonts-4] Create proper types for `<absolute-size>` and `<relativ…
Drop patches for `<absolute-size>` and `<relative-size>`
Drop patches for `<absolute-size>` and `<relative-size>` (#1796)
tidoust commentedon Jan 12, 2026
Spec was updated. And I was wrong: the syntax in
css-fonts-4can actually be extracted automatically, which means the syntax patch is no longer needed at all. I dropped it.New syntax with
xxx-largewill be released once #1783 can be merged. I'm closing this issue as addressed.Note: The spec encloses the syntax in square brackets, which aren't necessary when considering the syntax in isolation. This is not the only case where enclosing square brackets are used. We could try to normalize syntaxes in the curated data if there's a need for it. Sticking to what the spec defines in the meantime.
romainmenke commentedon Jan 12, 2026
Thank you @tidoust 🙇