- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 03 Sep 2025 16:16:46 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-grid-3][masonry] Make `item-tolerance` initial value `normal` ``, and agreed to the following: * `RESOLVED: change initial value of item-tolerance to 'normal'` <details><summary>The full IRC log of that discussion</summary> <alisonmaher> https://github.com/w3c/csswg-drafts/issues/10882<br> <JoshT> alisonmaher: two issues related to the issue<br> <JoshT> ... proposal to use 0 instead of 1em for initial value<br> <JoshT> ... may be less confusing for authors to see jumps<br> <JoshT> ... arguement against 0 is that it's not as accessible. less than 1px causes jumps in dom order<br> <JoshT> ... so proposed to keep 1em and see author feedback<br> <oriol> q+<br> <JoshT> ... column-gap has the same default<br> <JoshT> ... leave as 1em for now and use normal as initial value and compute to 1em<br> <astearns> ack oriol<br> <JoshT> oriol: agree that if we go for 0 for masonry, computed value should be normal<br> <JoshT> ... 1em for masonry and otherwise 0<br> <JoshT> ... preference still defaulting to 0 for masonry.<br> <astearns> q+<br> <JoshT> ... i agree 1em makes more sense. but preference is it may cause confusion<br> <JoshT> ... no one of the values in ???? does this<br> <astearns> s/????/masonry libraries/<br> <JoshT> ... providing a value that is small but not 0 may fail the expectations of authors<br> <JoshT> ... not sure if 1em will work well in general. something other than 0 may be good. 1em may be a random choice<br> <JoshT> ... have preference for 0 but not objecting to 1em. if we go for 0, may not need normal value<br> <JoshT> astearns: with the other issue about whether the default is 1em or 1lh, we can discuss separately for masonry. but making the default value 'normal' allows us to have that discussion for other layout modes that may need a different value<br> <astearns> ack astearns<br> <JoshT> oriol: masonry is strange if we say that the normal behaviour will be 0 because it will always be 0. but we can work out how to resolve this later<br> <astearns> ack fantasai<br> <JoshT> fantasai: I agree with oriol that it would be weird<br> <JoshT> ... but if we have a none 0 value, it should be normal.<br> <TabAtkins> +1<br> <JoshT> ... me and TabAtkins agree initial value should be 1em, to match row-gap<br> <JoshT> astearns: putting aside what it computes to, can we resolve that the initial value is 'normal' for now?<br> <JoshT> RESOLVED: change initial value of item-tolerance to 'normal'<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12111#issuecomment-3249911114 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 September 2025 16:16:47 UTC