W3C home > Mailing lists > Public > public-css-archive@w3.org > October 2019

Re: [csswg-drafts] [css-grid] grid area as element (#4416)

From: chvndb via GitHub <sysbot+gh@w3.org>
Date: Sun, 20 Oct 2019 09:46:45 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-544236973-1571564804-sysbot+gh@w3.org>
@fantasai indeed that does seem very similar as long as it also addresses the flow of items in the area. I missed that topic when looking through the issues.

@WebMechanic maybe you are diverging too much from the original question I posted. My suggestion implies a clear distinction between the parent grid flow and the grid-area flow. It would then be possible to have a different flow within an area that is "disconnected" from the parent grid. My example used a flex layout, but this could as easily been an absolute positioning (top, left, right, bottom) of items within the grid area. This is very different from you suggestion:

> One could think of the "areas" we get from flexbox are the additional rows/colums created when using flex-wrap: wrap.

How I understand your suggestion is that you are trying to look at the flow within the area as a continuation of the flow of the parent grid. That makes it much more complicated and creates many ambiguities in how to interpret what should happen or what to expect.

@Loirooriol That is exactly what I am trying to avoid as using wrapper elements restricts us when dealing with many different styling and layouting scenario's. As an example I could say that I only want the first three content items to appear in a more prominent place on top of my layout (e.g. a `main-content` grid area) when having less screen real estate and have the remaining content items appear in a secondary and smaller place at the bottom right next to other footer content that requires more scrolling to go through (e.g. a `secondary-content` grid area). The main content area could simple be a sub-grid while the secondary content area a flex layout. 

This becomes very difficult (or even impossible) when using wrapper elements as all content items are bound together by markup instead of semantics. 

GitHub Notification of comment by chvndb
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4416#issuecomment-544236973 using your GitHub account
Received on Sunday, 20 October 2019 09:46:47 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:55 UTC