- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 22 Nov 2023 17:45:02 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-grid-3][masonry] Reordering threshold`, and agreed to the following: * `RESOLVED: Accept some form of masonry slack property; exact algo TBD; exact name TBD` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> fantasai: In an earlier issue Ian suggested there should be some control over high sensitive masonry is to exact height differences<br> <TabAtkins> fantasai: Like if all your items are identical in size you'll lay out your content in perfect rows, straight across<br> <TabAtkins> fantasai: But if it's different sizes, column 2 was a little bit taller, you might skip from column 1 to column 3<br> <TabAtkins> fantasai: Ian suggested it might be useful to tweak the sensitivity so it's not just "is the difference 0", but to allow some amount of fudge factor<br> <TabAtkins> fantasai: So if the column 2 is only 10 px taller than column 1 and 3, you don't skip it, you place 1-2-3<br> <TabAtkins> fantasai: So do we want to add a control? Presuambly takes a length which is the fudge factor. And what do we call it?<br> <khush> q+<br> <TabAtkins> +1 to adding it<br> <TabAtkins> unsure about name, don't like any of the suggestions :/<br> <TabAtkins> khush: Have you seen use-cases where this is needed?<br> <TabAtkins> fantasai: The case Ian pointed out is - when you jump, it's harder to follow what's next. If you jump less often it's better to navigate for the user<br> <fantasai> One issue with masonry style layouts is that things can easily be visually out of order, e.g. if the current tracks are [100px, 99px] the next masonry item would be placed in the 2nd track, when the first would be more natural. A potentially solution to this is some user defined "threshold" to "place within the first track within Xpx of the smallest track"<br> <Rossen_> ack khush<br> <fantasai> masonry-threshold: <length><br> <fantasai> -- iank<br> <TabAtkins> q+<br> <Rossen_> ack TabAtkins<br> <fantasai> TabAtkins: Use case is as described, when the mortar columns are fairly ragged, it's fine to track across columns<br> <fantasai> TabAtkins: when there is some sort of order<br> <fantasai> TabAtkins: but when differences are very small, looks very strange to skip over something<br> <iank_> One important note as well is the simple algorithm for this doesn't work - there is a staircase case where the simple algorithm doesn't work.<br> <fantasai> TabAtkins: if your column height differences are minimal, it looks weird to have a gap<br> <fantasai> TabAtkins: better to have gap at the end of the row instead<br> <fantasai> TabAtkins: this is an ability that masonry libraries have; not sure how common, but definitely some<br> <TabAtkins> iank_: [restates irc comment]<br> <TabAtkins> iank_: where even if all the tracks are off by 1px it looks very strang eto select the first one<br> <TabAtkins> iank_: So there needs to be a precise algorithm written that tests against the cases<br> <SebastianZ> q+<br> <Rossen_> ack SebastianZ<br> <TabAtkins> SebastianZ: so we're just talking about regarding the height of the already palced content?<br> <TabAtkins> fantasai: right<br> <fantasai> masonry-slack?<br> <astearns> we should look to see what the masonry libraries use<br> <TabAtkins> TabAtkins: I think we can resolve to add this ability. Should discuss names, all the ones in the issue are more complex words than I like to use in properties<br> <TabAtkins> TabAtkins: But I really like the masonry-slack fantasai just suggested<br> <TabAtkins> proposed resolution: Accept some form of masonry slack property; exact algo TBD; exact name TBD<br> <TabAtkins> RESOLVED: Accept some form of masonry slack property; exact algo TBD; exact name TBD<br> <TabAtkins> Agree with astearns we should do a quick survey to see if libs have consistency in naming<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9328#issuecomment-1823217994 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 22 November 2023 17:45:04 UTC