- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Tue, 24 May 2016 13:09:07 -0700
- To: fantasai <fantasai.lists@inkedblade.net>
- Cc: www-style list <www-style@w3.org>
On Mon, May 23, 2016 at 2:04 PM, fantasai <fantasai.lists@inkedblade.net> wrote: > On 05/23/2016 03:40 PM, Eric A. Meyer wrote: >> On 23 May 2016, at 14:29, Tab Atkins Jr. wrote: >>> On Tue, May 17, 2016 at 2:51 PM, fantasai <fantasai.lists@inkedblade.net> >>> wrote: >>> >>>> * We are making subgrid behavior contingent on there not being >>>> any grid-template-* declarations, rather than merely ignoring >>>> them, with the hope that authors will not leave any such >>>> declarations lying around. Our goal is to allow for more >>>> sophisticated interleaving of subgrid and parent grid lines >>>> (e.g. 1-axis subgrids) using these properties. This may or may >>>> not work out as planned. :) >>> >>> >>> And in further discussion with dholbert, we decided *not* to do this - >>> the upgrade story is *way* too uncertain to rely on, so there's not a >>> good reason to try out carve out syntax. If we do 1-axis subgrid in >>> the future, we'll do so via a different 'display' value, or another >>> property, or something else new like that. >> >> Are you thinking something like 'display: subgrid-col' and >> 'display: subgrid-row' to achieve that 1-axis behavior? Not trying >> to pin you down to exact syntax or values or even patterns, but I'd >> like to get a sense of the thinking here. > > Another possibility would be 'grid-template-rows: subgrid <whatever>' > where the subgrid keyword means "no I really want this track listing, > ignore the other one". Right. Point is just "some clearly new syntax that is not possible today", rather than pretending we can do a clean upgrade. ~TJ
Received on Tuesday, 24 May 2016 20:09:55 UTC