W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2017

Re: [csswg-drafts] [css-sizing] Defer 'stretch' and 'fit-content' keywords to level 4

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 01 Nov 2017 23:28:44 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-341273524-1509578922-sysbot+gh@w3.org>
The Working Group just discussed `Defer 'stretch' and 'fit-content' keywords to level 4`, and agreed to the following resolutions:

* `RESOLVED: take stretch and fit-content to level 4 and dropping a note noting where they went and pointing to next level`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Defer 'stretch' and 'fit-content' keywords to level 4<br>
&lt;dael> github:  https://github.com/w3c/csswg-drafts/issues/1912<br>
&lt;dael> fantasai: TabAtkins and I noticed the majority of open issues or things we need to add is related to 'stretch'. The rest have a consistant definition, have been or have been discussed being shipped.<br>
&lt;dael> fantasai: Unless someone has a different opinion we'd like to drop these two props and then take the spec to CR once people have gotten a chance to check.<br>
&lt;dael> fremy: Reasonable.<br>
&lt;dael> dbaron: Shoudl we add a note where they were saying they were dropped?<br>
&lt;dael> fantasai: I can do that.<br>
&lt;dael> astearns: Obj to taking stretch and fit-content to level 4 and dropping a note noting where they went<br>
&lt;dbaron> ... and pointing to the next level<br>
&lt;dael> RESOLVED: take stretch and fit-content to level 4 and dropping a note noting where they went and pointing to next level<br>
&lt;dael> fantasai: [missed] The one with the argument relies on min-content and max-content to it doesn't depend ong stretch<br>
&lt;dael> astearns: Did anyone impl fit-content?<br>
&lt;dael> fantasai: I'm not sure, but I think the spec needs more work. My plan for L4 fwiw is to have stretch, fit-content, contain keyword (because we wanted to work on it with stretch), and add an aspect ratio feature.<br>
&lt;dbaron> I think [missed] was fantasai proposing that the fit-content() function stays in this level, but the fit-content keyword moves to the next level<br>
&lt;dael> fantasai: That's the plan for L4 and I think TabAtkins and I can draft that pretty easily.<br>
&lt;dael> astearns: I was just wondering if we were trying to move sizing 3 to CR if fit-content would need to move for impl status. but that can happen when we get to next publishing stage.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1912#issuecomment-341273524 using your GitHub account
Received on Wednesday, 1 November 2017 23:28:45 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 1 November 2017 23:28:46 UTC