- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Jul 2024 16:12:26 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `should calc-size() and interpolate-size apply to grid-template-rows and grid-template-columns?`, and agreed to the following: * `RESOLVED: remove grid-template properties from the list of properties that calc-size is valid for and that interpolate-size works on` <details><summary>The full IRC log of that discussion</summary> <noamr> dbaron: hoping this would be quick. earlier in calc-size I've given a list of props it should work on<br> <noamr> dbaron: width/height/flex-sizes/grid-template-rows/template-columns/.. and equivalents. see in issue for full list<br> <noamr> dbaron: proposing to remove the grid ones for a few reasons. I thought it would be more doable than Ian<br> <noamr> dbaron: thought I was getting it done, but the approach doesn't work at all for division of length and unit algebra, both highly requested, speced but perhaps not implemented<br> <noamr> dbaron: basic conclusion after trying, there is no reasonable way to mix calc-size/interpolate-size with distribution over grid tracks, algebra over length<br> <noamr> dbaron: conclusion: not try to do it for grid properties, save initial version for the other properties and not the others<br> <noamr> dbaron: this might mean that if we figure this out in the future we might need to add a new opt-in value. we might not. but that's the down side<br> <noamr> dbaron: main reason to remove the grid props is that I don't see how to do it<br> <noamr> astearns: questions or concerns?<br> <TabAtkins> If dbaron can't figure it out, I doubt I could either, +1<br> <emilio> Sounds fair :)<br> <astearns> ack fantasai<br> <noamr> fantasai: how would this affect the syntax of the interpolate-size if we want to exend in the future?<br> <noamr> dbaron: we'd have to add a keyword like "also allow grid"<br> <noamr> fantasai: remind me of current values?<br> <noamr> dbaron: numeric only, allow-keywords<br> <TabAtkins> allow-keywords allow-grid-template<br> <TabAtkins> something like that<br> <noamr> fantasai: so we'll have "allow-grid" or something<br> <noamr> dbaron: something like that<br> <noamr> fantasai: sounds reasonable<br> <noamr> astearns: can this affect other props in the future. Anything left off the list dbaron?<br> <noamr> dbaron: only one possible candidate, something with column (column-width)?<br> <noamr> iank_: yes, it's column-width and the length properties<br> <noamr> astearns: it's possible we'd have some future extensions with more keywords<br> <noamr> astearns: seems reasonable if that ever happens<br> <noamr> dbaron: double hypthetical. need to do that if we found a way to do it and that by doing it would be a compat issue. for columns that's unlikely a compat issue<br> <noamr> astearns: any other q or comment?<br> <noamr> astearn: proposed resolution: remove grid-template properties from the list of properties that calc-size is valid for and that interpolate-size works on<br> <noamr> astearns: objections to removing grid-template-* properties from this feature?<br> <astearns> RESOLVED: remove grid-template properties from the list of properties that calc-size is valid for and that interpolate-size works on<br> <masonf> (the all-caps RESOLVED matters)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10618#issuecomment-2260884029 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 July 2024 16:12:27 UTC