search

w3c / webref

Machine-readable references of terms defined in web browser specifications
https://w3c.github.io/webref/
MIT License
295 stars 73 forks source link

No json shows `anchor-size()` can be used as value for sizing properties #1312

Closed OnkarRuikar closed 1 month ago

OnkarRuikar commented 1 month ago

LIke stretch and fit-content values the css-anchor-position-1.json needs to show width and other properties take anchor-size() as value.

tidoust commented 1 month ago

As done in css-sizing-4, css-anchor-position would ideally list the impacted CSS properties in a table with a "New Values" row instead of only saying so in prose.

On top of allowing the crawler to report that information automatically in the extract, this would help clarify what exact properties can take anchor-size() as value. For example, the prose links to the definition of sizing properties in css-sizing-3, which has a note that targets css-logical-1. Can anchor-size() also be used with the flow-relative properties defined in css-logical-1? (Or maybe that just does not make any sense?)

Also, if I'm reading things correctly, it seems the CSS WG resolved to extend the list of properties on which anchor-size() could be used not long ago, see https://github.com/w3c/csswg-drafts/issues/9827#issuecomment-2160430157.

If there's an issue opened against the spec, we could add a CSS patch to add "New values" entries in the css-anchor-position CSS extract (we try to always associate patches with issues so that we know when to drop it).

OnkarRuikar commented 1 month ago

Can anchor-size() also be used with the flow-relative properties defined in css-logical-1?

It looks like it does.

If there's an issue opened against the spec, we could add a CSS patch to add "New values" entries in the css-anchor-position CSS extract (we try to always associate patches with issues so that we know when to drop it).

I've raised an issue in the spec https://github.com/w3c/csswg-drafts/issues/10764

OnkarRuikar commented 1 month ago

If there's an issue opened against the spec, we could add a CSS patch to add "New values" entries in the css-anchor-position CSS extract (we try to always associate patches with issues so that we know when to drop it).

We do not need a patch now. After the requested spec update, the values are reflected in the webref. If you feel the changes are right then please close the issue.

tidoust commented 1 month ago

Great, thanks for reporting the issue!