- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 11 Sep 2024 16:13:52 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-grid-3] FPWD for Masonry Layout`, and agreed to the following: * `RESOLVED: FPWD for Grid 3` <details><summary>The full IRC log of that discussion</summary> <chrishtr> q+<br> <TabAtkins> fantasai: Tab and I got together - we figured out how to do mixed intrisnic tracks, and that removed most of the differences. we made a merged single draft with both proposals<br> <TabAtkins> fantasai: Differences are largely syntactic, they're listed as "grid-integrated" or "grid-independent"<br> <TabAtkins> fantasai: Changes are the properties from display:masonry proposal, you'll notice masonry-template-tracks has the same syntax now as grid-template-columns<br> <TabAtkins> fantasai: We also sketched the optimizations for track sizing that should make things work faster<br> <TabAtkins> fantasai: And how to handle sub-masonry to avoid the exponential aspects of nesting them.<br> <TabAtkins> fantasai: Probably a little left to do with nesting of subgrids, but should handle the major parts<br> <TabAtkins> fantasai: Integrated the 'masonry-slack' property, it was 'masonry-threshold' when we discussed it in the past<br> <TabAtkins> fantasai: We did edits for collapsing tracks for auto-fit; there were some details not discussed in the issue so please take a look if you're interested. We had to define a heuristic for what tracks were "occupied"<br> <TabAtkins> fantasai: Added row-reverse, column-reverse, and column-reverse for the Grid properties, and similar for masrony<br> <TabAtkins> fantasai: And Tab's draft had repeat(auto-areas)<br> <TabAtkins> fantasai: Issue open on whether we need it<br> <TabAtkins> fantasai: Aside from the fallback behavior, its behavior is already part of grid<br> <TabAtkins> fantasai: Also we added an a11y section, outlines some of the potential problems. References reading-flow property<br> <fantasai> https://drafts.csswg.org/css-grid-3/#order-accessibility<br> <TabAtkins> fantasai: and talks about some ways to avoid the need for back-tracking<br> <TabAtkins> fantasai: So that's the current draft. We think this represents the discussion well. At this point there's three impls of Masonry layout, two under grid-integrated and one under grid-independent. \<br> <TabAtkins> fantasai: Think it's important to get the draft out, post for TAG review, and get broader input from the community so we can refine the draft further.<br> <astearns> ack chrishtr<br> <TabAtkins> chrishtr: Thanks Elika and Tab to integrate these alternatives<br> <TabAtkins> chrishtr: Happy to see this go to fpwd for wider community feedback, particularly webdevs<br> <TabAtkins> chrishtr: one question I have is, does the current draft point out differences in functionality between the alternatives?<br> <TabAtkins> chrishtr: My understanding is there are some things possible in grid-independent that aren't in grid-integrated<br> <fantasai> TabAtkins: Some differences, but much closer<br> <fantasai> TabAtkins: not huge either<br> <fantasai> fantasai: which differences, other than initial value?<br> <fantasai> TabAtkins: repetition of intrinsic track sizes<br> <fantasai> TabAtkins: which I think should be the initial value<br> <fantasai> fantasai: With mixed track sizing, no longer guaranteed to have the same size, so is that even still possible?<br> <fantasai> TabAtkins: need to review<br> <fantasai> astearns: should have an issue to track each difference<br> <TabAtkins> astearns: Any more comments?<br> <TabAtkins> astearns: Concerns about publishing fpwd?<br> <TabAtkins> RESOLVED: FPWD for Grid 3<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8195#issuecomment-2344098078 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 11 September 2024 16:13:52 UTC