- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 10 Apr 2018 12:19:23 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `Review state of Grid Level 2, figure out next steps`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Review state of Grid Level 2, figure out next steps<br> <fantasai> https://www.w3.org/TR/css-grid-2/<br> <dael> fantasai: Issue with grid L2 it has some proposals and no feedback. I can do anything to go forward<br> <dael> fantasai: Open issues are like here's 2 proposals for subgrid, which do we want?<br> <dael> fantasai: I wanted to bring this up because there's strong requests from the community to do this, but the spec for subgrid is there's 2 specs for subgrid. I don't know what to do next.<br> <dael> florian: Is there author feedback?<br> <dael> rachelandrew: I have feedback. Authors really want subgrid. The use cases I've seen are tied to dimension sub grid....the proposal that was pulled from L1 wouldn't solve them. People want the columns to be the sub grid. They don't want to define the rows. Having to locked to both dimenstions would be more frustrating then useful. Things I"ve seen assumed one dimension.<br> <dael> fantasai: Proposal is to resolve on per axis subgrids.<br> <dael> Rossen: Didn't we decide in tokyo?<br> <dael> tantek: We added it as a possibility in tokyo.<br> <dael> Rossen: sgtm. I thought we did that.<br> <dael> Rossen: This is the 1.5 dimension model?<br> <dael> fantasai: No, the way we set thing sup there's not many changes from one version to the other. Differences are in green. Main change is for per axis you need to ensure that if you're interweving the algo of the parent and child grids.<br> <dael> fantasai: Algo is all defined. That's where spec is at. I think it's complete mostly.<br> <dael> astearns: Do we have impl?<br> <dael> fantasai: I don't think anyone is working on sub grids.<br> <dael> TabAtkins: Mats was interested and opposed the non-per axis. That's what Igalia part impl.<br> <dael> rego: We didn't impl anything yet.<br> <tantek> Mats is working on it, see the Firefox subgrid meta bug (with dependent implementation bugs) https://bugzilla.mozilla.org/show_bug.cgi?id=1240834<br> <dael> fantasai: Syntatic difference the per axis has a subgrid keyword on grid-template-rows and grid-template-columns. Just one was a keyword on grid-template.<br> <dael> astearns: Would anyone object to single axis subgrid?<br> <dael> TabAtkins: No one has described how to do it yet.<br> <dael> fantasai: It's in the spec. Here's the algo (section 2.4)<br> <dael> astearns: It's spec as a diff to a doc with both.<br> <dael> fantasai: It inlines everything in. It just has two colors of ink.<br> <dael> astearns: Anyone besides TabAtkins have concerns on single axis subgrid.<br> <dael> rego: Seems more complex to impl but it would be good to know use cases. If there are clear use cases where we need this it's fine.<br> <dael> rachelandrew: I brought use cases to the last F2F but I rarely see something from an author that works for double axis. An ecommerce site that has a template where they want it to work no matter if there's 2 rows or 6 rows of stuff.<br> <dael> rachelandrew: Let me see if I can find the examples<br> <dael> astearns: Would people object to 2 axis subgrid?<br> <dael> florian: I think rachelandrew would.<br> <rachelandrew> https://codepen.io/rachelandrew/project/editor/68cc7a5da9cfbb56c6e8366d7d92e6ba<br> <dael> astearns: I'm hearing some people for and against single axis subgrid but I haven't heard opinions on 2 axis besides everyone thought it was too hard to get to for the first level of grid.<br> <tantek> IIRC, all variants of subgrid were too much for grid level 1<br> <rachelandrew> this is a better view, some examples https://codepen.io/rachelandrew/project/full/68cc7a5da9cfbb56c6e8366d7d92e6ba/XWYGMD/<br> <dael> Rossen: I still agree it was a good move to hold it back. To your second point as to if one or two axis is what we want, now that we can reason about it and think hoelistically the one axis is an easy shortcut to cover some use cases but during Tokyo I heard enough compelling reasons to have the per axis. I will admit I haven't reviewed spec. But I prefer the per axis one. I don't think there will be all that much work per axis, at least in our impl.<br> <dael> astearns: Perhaps we could leave it at peole should review the spec and look at the use cases and then come back soon?<br> <dael> rachelandrew: I could probably get more use cases now that people are using grid.<br> <dael> astearns: Is there an issue for choose which appoach?<br> <dael> fantasai: Yep.<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/2280<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/2280<br> <dael> astearns: I suggest we continue discussing in that issue.<br> <dael> astearns: Anything else?<br> <dael> fantasai: Whe do we want to return?<br> <dael> Rossen: End of F2F.<br> <dael> astearns: WE can try and bring this up end of Thursday. Then perhaps we can make a decision.<br> <dael> astearns: Please take breaks or lunch time if as you read you have questions.<br> <dael> dbaron: Would it help to get someone on a call.<br> <dbaron> s/someone/Mats/<br> <dael> fantasai: It would be good to have Mats look and reply on github.<br> <dael> fantasai: I haven't heard from him.<br> <dael> dbaron: If you want me to poke him can you send me what you want me to do?<br> <dael> fantasai: Review the spec and comment.<br> <dael> florian: Also express a preference? Or he always has.<br> <fantasai> fantasai: And if there's nothing wrong with it say it's good<br> <dael> astearns: Other part of grid L2 as aspect ratio contols<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/1116<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/2280<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2280#issuecomment-380078302 using your GitHub account
Received on Tuesday, 10 April 2018 12:19:25 UTC