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

Re: [csswg-drafts] [css-grid-2][css-grid] `grid-template-rows/columns` Computed / Resolved Values for 'subgrid' values (#4362)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 09 Oct 2019 16:59:33 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-540092172-1570640372-sysbot+gh@w3.org>
The CSS Working Group just discussed `` `grid-template-rows/columns` Computed / Resolved Values for 'subgrid' values``, and agreed to the following:

* `RESOLVED: Accept Mat's proposal which is that resolved value unwraps repeat notations and does not insert track sizes for subgrid`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: `grid-template-rows/columns` Computed / Resolved Values for 'subgrid' values<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/4362<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4362<br>
&lt;dael> fantasai: Just accept Mats proposal<br>
&lt;dael> astearns: Opinions?<br>
&lt;dael> Rossen_: Wish I had time to read it.<br>
&lt;dael> Rossen_: This doesn't sound like something needed right now. Resolve next week?<br>
&lt;dael> jensimmons: Can fantasai explain and then Rossen_ you can feel you understand? I don't want to postpone because we're trying to ship subgrid<br>
&lt;dael> fantasai: Issues is when getting resolved value, value from gCS, what that value is not well defined. Regular grids resolved value expands all repititions so you have number of tracks/columns. Mats proposal is same for subgrid but don't include length b/c that's not valid value.<br>
&lt;dael> fantasai: You would say subgrid and then a list of all the line names.<br>
&lt;dael> fantasai: Example in the bottom makes it clear<br>
&lt;dael> Rossen_: In this way it will be...subgrid columns will be serialized as part of grid col?<br>
&lt;dael> fantasai: grid-template-columns is property, subgrid keyword. Optional line names which are matched up. Can use repeat notation<br>
&lt;dael> Rossen_: Grid-template-columns would resolve to what he suggests in very last sentence?<br>
&lt;dael> Rossen_: Is that the expected behavior?<br>
&lt;dael> fantasai: Yeah<br>
&lt;dael> fantasai: WE do the same thing as for regular grids, but we don't specify sizes in resolved value. Otherwise same rules for expanding repetitions<br>
&lt;dael> Rossen_: Going through examples to figure out if it's lossy for what you can reconstruct<br>
&lt;dael> fantasai: It is lossy in same way as current without subgrid. We return resolved style, not computed.<br>
&lt;dael> Rossen_: I'm trying to figure out if it's more lossy, but seems about same<br>
&lt;dael> fantasai: Yeah<br>
&lt;dael> Rossen_: Doesn't sound bad<br>
&lt;dael> fantasai: Alternatives is to fill in all sizes, but then can't read it back in. Want it to roundtrip<br>
&lt;dael> Rossen_: Agree<br>
&lt;dael> fantasai: Other is to not unwrap but that's inconsistent with regular grids.<br>
&lt;dael> Rossen_: Yeah. That would have been my pref but we are where we are.<br>
&lt;dael> Rossen_: This seems consistent. Not opposed<br>
&lt;dael> astearns: Prop: Accept Mats' suggestion which preserves consistency with the rest of grid but allows subgrid values to roundtrip<br>
&lt;dael> fantasai: Prop: Accept Mat's proposal which is that resolved value unwraps repeat notations and does not insert track sizes for subgrid<br>
&lt;dael> astearns: Objections?<br>
&lt;dael> RESOLVED: Accept Mat's proposal which is that resolved value unwraps repeat notations and does not insert track sizes for subgrid<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4362#issuecomment-540092172 using your GitHub account
Received on Wednesday, 9 October 2019 16:59:35 UTC

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