- From: Oriol Brufau via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Mar 2023 23:37:56 +0000
- To: public-css-archive@w3.org
Maybe "standalone axis" is not the best terminology if it's not a grid, but the spec covers this case in https://drafts.csswg.org/css-grid-2/#resolved-track-list-standalone > Otherwise, (e.g. when the element has [display: none](https://drafts.csswg.org/css-display-4/#propdef-display) or **is not a [grid container](https://drafts.csswg.org/css-grid-2/#grid-container)**) the resolved value is simply the [computed value](https://drafts.csswg.org/css-cascade-5/#computed-value). I think "`<integer>` computed" may mean that e.g. `calc(1em / 1px)` should become `16`. It doesn't mean that you should expand the repeat. The internal computed value should never do that, only the resolved value from `getComputedStyle` in some cases. This affects interpolation, e.g. `repeat(2, 100px)` and `repeat(1, 200px 200px)` interpolate discretely, even though `repeat(2, 100px)` and `repeat(2, 200px)` would be smooth. See https://drafts.csswg.org/css-grid-2/#repeat-interpolation -- GitHub Notification of comment by Loirooriol Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8555#issuecomment-1464645035 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 10 March 2023 23:37:58 UTC