- From: Jacob Pratt <jhprattdev@gmail.com>
- Date: Mon, 22 Jan 2018 22:44:30 -0500
- To: Sebastian Malton <sebastian@malton.name>, www-style@w3.org
- Message-ID: <CAAFMpDr94ZvQcCEYuzBu7+FaVJHOmWkCfpnw2=H2LY11kkpyWQ@mail.gmail.com>
I thought subgrid was still being promoted, though I haven't been following it too closely. Taking the track with the plurality would certainly make more sense. It may not necessarily have >=50%, though. jhpratt On Mon, Jan 22, 2018 at 10:41 PM, Sebastian Malton <sebastian@malton.name> wrote: > Hello, > I don't think that there is currently. However, some notes: is subgrid > still being promoted? Since we have grids within grids by just css > definition. > > Second, I would say that concerning the multiple rows and columns problem. > I would say it should be based off of covering 50% or more of the element. > Where that amount is configurable in the grid. This way it can be decided > by the designer. > > Sebastian Malton > *From:* jhprattdev@gmail.com > *Sent:* January 22, 2018 10:34 PM > *To:* www-style@w3.org > *Subject:* [css-grid] :nth-row, :nth-column selectors and similar > > All, > > Are there any active proposals (or any that have been shot down) regarding > table-like selectors for CSS Grid? Namely the following: > > - nth-row > - nth-column > - nth-last-row > - nth-last-column > - first-row > - first-column > - last-row > - last-column > > These selectors could prove incredibly useful with `auto-fit`, and > especially once subgrid is implemented. > > The use case would be similar to that of tables, but for cases where > tables are not necessarily appropriate to be used. > > The one problem I can think of: how will elements that span multiple > tracks be handled? My naïve solution would be to use the top left cell, > though I've no clue on the benefits and drawbacks from such. > > jhpratt >
Received on Tuesday, 23 January 2018 03:44:56 UTC