|Summary:||[css-grid] Add support for subgrid (Grid Level 2)|
|Product:||WebKit||Reporter:||Moritz Mahringer <moritz.mahringer>|
|Severity:||Normal||CC:||709922234, daytonlowell, jensimmons, jfernandez, kyle.bavender, michaelcpuckett, miriam, mjs, moritz.mahringer, obrufau, olestr, rego, tannerhodges, webkit-bug-importer|
Description Moritz Mahringer 2019-09-23 11:27:36 PDT
I'd like to suggest adding support for CSS Grid Layout Module Level 2 (https://www.w3.org/TR/css-grid-2/). It has been implemented by Firefox/Gecko and ships in Firefox 69 (https://bugzilla.mozilla.org/show_bug.cgi?id=1496502). Chromium seems to be working on it, albeit slowly / not prioritized (https://bugs.chromium.org/p/chromium/issues/detail?id=618969). I think this will improve mobile and responsive data layouts significantly.
Comment 1 Miriam Suzanne 2019-10-22 13:35:18 PDT
Subgrid makes the grid layout specification much more useful across a wide range of use-cases. Without subgrid, authors resort to non-semantic markup, `display: contents`, and explicit sizing to get even a small fraction of what it can do. This can be the difference between spending minutes or days building a layout properly. With support landing in Firefox 70 (Dec 3) it would be lovely to see compatibility in other browsers.
Comment 3 Ole Strøm 2021-02-11 07:39:28 PST
It seems Chrome is making steady progress on their implementation. After reading their issues on this, they're first focusing on landing their new grid implementation, and after that subgrid will be trivial to add. That's nice. So I wondered what's the status on Safari, seeing that it would be the only blocker when Chrome gets it down (https://caniuse.com/css-subgrid). Seems there's no mention of it on https://webkit.org/status/#?search=grid and no activity on this issue in over a year. What's up? It would be awful if we have to wait to use subgrids until Safari supports it as well. It would sadly not be the first time such a thing has happened. While not exactly for this issue, it is a little related. On my fairly regular projects the past year or two, where it would have been IE before, it's now Safari that's problematic and lagging behind. I see more and more comments from developers feeling the same. Causing us to have to compromise with workarounds or polyfills where possible. Some examples: https://caniuse.com/flexbox-gap https://caniuse.com/input-datetime https://caniuse.com/dialog https://caniuse.com/css-scroll-behavior https://caniuse.com/css-overscroll-behavior https://caniuse.com/js-regexp-lookbehind I do feel like the tide is turning. Almost all of the above are landing soon enough. I just hope we don't have to wait two years for this one as well.
Comment 4 Jen Simmons 2021-02-12 11:57:38 PST
Thanks for your comment, Ole. And for making a list of six other things you'd like to see implemented. We do hear you.