- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Apr 2025 20:36:10 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-grid] Decide on a name for `item-slack` ``, and agreed to the following: * `SUMMARY: Contemplate replacing 'item-' with 'flow-'` * `RESOLVED: rename item-slack to item-tolerance ... for now.` <details><summary>The full IRC log of that discussion</summary> <kbabbitt> oriol: we have this property item-slack<br> <kbabbitt> ... what it does is allow diverging from sorting items into shortest track<br> <kbabbitt> .. with tracks filled to a similar amount it allows following source order instead of shortest<br> <kbabbitt> .. value of 0 means strictly shortest track<br> <kbabbitt> ... value of infinity means strictly source order<br> <kbabbitt> ... this is named 'item-slack' in spec<br> <kbabbitt> ... but we didn't resolve on that name<br> <kbabbitt> ... not fond of "slack" as non-native Engish speaker<br> <kbabbitt> ... there were also some other ideas like strictness, or ??<br> <kbabbitt> ... they seem to imply a higher value will implyu more strictness<br> <kbabbitt> ... where it's the opposite<br> <astearns> s/??/sensitivity/<br> <kbabbitt> ... other ideas were threshold, adjust, skip<br> <kbabbitt> ... I propose 'tolerance'<br> <kbabbitt> ... which some people were recommending recently<br> <bkardell> s/implyu/imply<br> <dbaron> We can always change the property values to match the name.<br> <kbabbitt> ... when I proposed this it was with masonry prefix<br> <kbabbitt> ... now that it could be item tolerance, could be more confusing of how you're adding tolerance<br> <kbabbitt> ... astearns proposed 'item-fit'<br> <kbabbitt> ... someone also suggested "cram"<br> <jensimmons> q+<br> <kbabbitt> ... but people liked the word tolerance<br> <kbabbitt> fantasai: cram doesn't work for all the cases we're talking about<br> <kbabbitt> TabAtkins: can't imply squeezing or stretching<br> <kbabbitt> ... can be used for either<br> <astearns> ack jensimmons<br> <fantasai> florian: "fuzz"?<br> <kbabbitt> jensimmons: let's rename it<br> <kbabbitt> ... I like tolerance too<br> <TabAtkins> I'm okay with 'tolerance'<br> <kbabbitt> ... it is true that it is confusing by itself<br> <kbabbitt> ... item-fit-tolerance is good but long<br> <TabAtkins> i don't super like any of the shorter words than tolerance<br> <kbabbitt> ... would be all for replacing slack with fit-tolerance<br> <kbabbitt> TabAtkins: also a fan of tolerance<br> <kbabbitt> astearns: everyone ok with adding 'fit'?<br> <kbabbitt> fantasai: don't love it but don't have better suggestion<br> <kbabbitt> astearns: we're not tolerating the item<br> <kbabbitt> TabAtkins: all the item properties are about placing item, so item-tolerance would also be about placing the item<br> <kbabbitt> ... think it already suggests roughly what we're aiming at<br> <kizu> +1 to tolerance as well<br> <kbabbitt> astearns: item-fit-tolerance was my best name<br> <kbabbitt> TabAtkins: I'm always looking out for property name lengths<br> <kbabbitt> dholbert: item-fit reminds me of object-fit which is unrelated<br> <kbabbitt> ... that slight overlap is confusing<br> <kbabbitt> dbaron: don't reject names because they don't go with values<br> <kbabbitt> ... can always change values to go with names<br> <kbabbitt> TabAtkins: here the values are lengths not keywords<br> <kbabbitt> fantasai: what if we rename item-flow to flow<br> <kbabbitt> ... then it would be flow-tolerance, flow-direction, ...<br> <kbabbitt> TabAtkins: doesn't that land us against flow layout module that describes block?<br> <ethanjv> I like flow<br> <kbabbitt> fantasai: besides display keyword is awkward<br> <kbabbitt> ... otherwise work really well<br> <ethanjv> https://drafts.csswg.org/css-grid-3/#flow-control<br> <kbabbitt> TabAtkins: can we look at item properties real quick?<br> <kbabbitt> fantasai: replace 'item' prefix with 'flow'<br> <kbabbitt> ... then 'item-flow' becomes 'flow'<br> <kbabbitt> TabAtkins: means we can't have a shorthand<br> <kbabbitt> fantasai: item-flow -> flow is the shorthand<br> <kbabbitt> kbabbitt: "flow-pack"?<br> <kbabbitt> fantasai: yes<br> <kbabbitt> astearns: don't want to resolve on this change right away<br> <kbabbitt> astearns: Proposed: rename item-slack to item-tolerance<br> <fantasai> SUMMARY: Contemplate replacing 'item-' with 'flow-'<br> <kbabbitt> bkardell: it's very difficult for people looking in to understand stability of our decisions<br> <kbabbitt> ... we should say, as a currently best working answer but probably to be re-bikeshedded later<br> <kbabbitt> astearns: that applies to all our resolutions<br> <kbabbitt> bkardell: should be more specific here since it's being cited in intents to ship<br> <oriol> Hard to hear Brian<br> <kbabbitt> TabAtkins: this one is pretty explicitly tentative<br> <kbabbitt> bkardell: can we put the word tenative in the resolution?<br> <kbabbitt> florian: all our decisions can be revisited, when we know they will be, dont print your book yet<br> <kbabbitt> astearns: Proposed: rename item-slack to item-tolerance ... for now.<br> <kbabbitt> astearns: objections?<br> <kbabbitt> RESOLVED: rename item-slack to item-tolerance ... for now.<br> <kurt> The spec uses the word "threshold" - The item-slack property specifies what the threshold is for considering tracks to be “the same height”, causing them to fill in order.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10884#issuecomment-2773675152 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 April 2025 20:36:11 UTC