The required “Debuggability” section was left empty. Please follow https://goo.gle/devtools-checklist and elaborate on how developers would inspect & debug this new feature. Per the guide, we need to ensure DevTools supports basic editing of the new CSS properties and values — which would likely work out-of-the-box anyhow. Please elaborate.
On Tue, Jan 18, 2022 at 6:42 PM 'Ethan Jimenez' via blink-dev < [email protected]> wrote: > *Contact emails* > > [email protected] > > *Explainer* > > None > > *Specification* > > https://drafts.csswg.org/css-grid-2 > > *Design docs* > > https://docs.google.com/document/d/1cpsCmzdDlXUKtMxOUKIoJFyLH54mLVhZnam_z0PriO0/edit?usp=sharing > > *Summary* > > Implements the CSS Grid Layout Module Level 2 specification, which > introduces the concept of a "subgrid" to nested grid containers. > > *Blink component* > > Blink>CSS > <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS> > > *Motivation* > > The problem CSS Subgrid solves is inheritance within nested grid > containers: only direct children of a grid container are aware of its > parent's grid properties, e.g., the size of its tracks, the names of each > grid line. Whenever web authors work with a grid spanning some area within > another grid, the children of the innermost grid are unaware of the > outermost grid structure, which could potentially be a disadvantage if > authors want those items to be aligned to other descendants of the > outermost grid. A "subgrid" is a nested grid container whose row and column > definitions are deferred to its parent; with such concept in mind, the > problem above is mitigated by inheriting the grid properties and alignment > from the spanned grid area in its parent grid. > > *Initial public proposal* > > > *Search tags* > > subgrid <https://chromestatus.com/features#tags:subgrid>, css-grid-2 > <https://chromestatus.com/features#tags:css-grid-2>, css > <https://chromestatus.com/features#tags:css> > > *TAG review* > > > *TAG review status* > > Not applicable > > *Risks* > > *Interoperability and Compatibility* > > This is a well-defined specification from the W3C, so we would be > addressing some interoperability gaps instead of causing them. > > *Gecko*: Shipped/Shipping > > *WebKit*: Positive > > *Web developers*: Strongly positive > > *Other signals*: > > *Debuggability* > > > *Is this feature fully tested by **web-platform-tests* > <https://chromium.googlesource.com/chromium/src/+/master/docs/testing/web_platform_tests.md> > *?* > > Yes > > *Flag name* > > > > *Requires code in //chrome?* > > False > > *Tracking bug* > > https://crbug.com/618969 > > *Estimated milestones* > > No milestones specified > > *Link to entry on the Chrome Platform Status* > > https://chromestatus.com/feature/5663795354533888 > > This intent message was generated by Chrome Platform Status > <https://chromestatus.com/>. > > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/MN2PR00MB06691936F5BB8575F43A9704BC569%40MN2PR00MB0669.namprd00.prod.outlook.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/MN2PR00MB06691936F5BB8575F43A9704BC569%40MN2PR00MB0669.namprd00.prod.outlook.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADizRgahta5WoNwYezq1959cAVVAW39ky1cDg8yRsw8w_prKLw%40mail.gmail.com.
