W3C home > Mailing lists > Public > public-css-archive@w3.org > January 2017

Re: [csswg-drafts] [css-grid] Regarding the 'subgrid' feature

From: Rachel Andrew via GitHub <sysbot+gh@w3.org>
Date: Thu, 19 Jan 2017 06:08:51 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-273690364-1484806129-sysbot+gh@w3.org>
I've been very vocal about my belief that subgrid is a requirement, 
and have been talking about this with authors and looking at use cases
 for the last couple of years [1].

The revised specification came about after a conversation with 
developers from Igalia [2], as an attempt to move the feature forward.
 Given that this has not resulted in any implementor doing so, I would
 be inclined to agree with Mats that the feature should be more 
clearly worked through, rather than this revised attempt pushed into 
L1. 

The revised spec solves a class of issues that authors expect grid to 
solve for them. For example in this post[3], the author wants to be 
able to line up the internals of a set of boxes laid out by grid. In 
this case we know the number of rows required in the subgrid so the 
fact that subgrids are in both dimensions would not be an issue. There
 are a number of cases however [4]where people will want more 
auto-placement of items in a subgrid, and I don't see how this will 
work with the revised spec.

It's been relatively difficult to get good author use cases for more 
than the most trivial of things, with grid behind a flag. I'm starting
 to see that pick up now as people realise this is shipping in 
browsers. I think in 6 months time we're going to have a lot more to 
work with in terms of seeing how people really want to use this 
feature. My fear in punting it to L2, without clear interest from 
implementors is that it disappears into some distant future. 

So at this stage I agree with Mats, this feature still needs a 
significant amount of discussion, it needs more author use cases 
(which I will continue to collect as I talk to authors). Grid is 
already at CR and my understanding in terms of process is that Grid 
can't exit CR with features that do not have two interoperable 
implementations, so a decision will need to be made at some point 
about subgrid. Whatever that decision is I very much hope that it 
comes along with interest from both the WG and implementors to move 
this feature along. My feeling is we will start to get a lot of demand
 for it from authors very soon.

1. [Modern CSS Layout Power and 
Responsibility](https://rachelandrew.co.uk/archives/2015/07/28/modern-css-layout-power-and-responsibility/)
2. [Subgrids thinking out 
loud](http://blogs.igalia.com/mrego/2016/02/12/subgrids-thinking-out-loud/)
3. [CSS Grid AMA Issue 
13](https://github.com/rachelandrew/cssgrid-ama/issues/13)
4. [A Revised Subgrid 
Specification](https://rachelandrew.co.uk/archives/2016/04/25/a-revised-subgrid-specification/)

-- 
GitHub Notification of comment by rachelandrew
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/958#issuecomment-273690364 
using your GitHub account
Received on Thursday, 19 January 2017 06:08:59 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:26:37 UTC