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

Re: [csswg-drafts] [css-sizing-4] Use cases for explicit intrinsic-size (#4585)

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Tue, 20 Oct 2020 22:28:23 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-713176382-1603232902-sysbot+gh@w3.org>
The CSS Working Group just discussed `Sizing`.

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> Topic: Sizing<br>
&lt;Rossen_> github:https://github.com/w3c/csswg-drafts/issues/4585<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/4585#issuecomment-701595999<br>
&lt;tantek> Rossen_: who wants to summarize?<br>
&lt;tantek> fantasai: we created this issue to collect use-cases for the control over use-cases over intrinsic sizes of boxes<br>
&lt;tantek> ... we have 3 maybe 4<br>
&lt;tantek> ... one is webkit like behavior<br>
&lt;tantek> ... another is zeroing out the ... of scrolling containers<br>
&lt;cbiesinger> s/.../min-content contribution/<br>
&lt;tantek> ... another one is zeroing out the max content contribution when there is a zero size or max size in that axis<br>
&lt;cbiesinger> s/max content/min content/<br>
&lt;tantek> ... someone wanted to have a box that had the same behavior as a replaced element<br>
&lt;tantek> ... they were able to replicate a lot with our aspect ratio stuff<br>
&lt;tantek> ... but this is a quirk of how replaced elements behave<br>
&lt;Rossen_> q<br>
&lt;tantek> fantasai: q to wg, do we want to design a property to switch between these different values?<br>
&lt;tantek> ... q2 to wg, are there are other cases we should add to this<br>
&lt;tantek> Rossen_: opinions?<br>
&lt;fantasai> s/behave/behave that's unrelated to aspect ratios/<br>
&lt;tantek> (awkward silence)<br>
&lt;tantek> Rossen_: do we care enough about this? or we can also move on if there is not enough interest here<br>
&lt;tantek> ... there was interest here. in terms of behavior what do we want?<br>
&lt;tantek> ... dbaron also dumped a bunch of mozilla bugs that were a good indicator that we need to look into solving this<br>
&lt;tantek> ... i don't see anyone on the queue or engaging<br>
&lt;tantek> ... shall we close the issue with no change?<br>
&lt;tantek> cbiesinger: i would really like to have this property<br>
&lt;tantek> ... the second part was requested by me because I know some people who want to use this on their websites<br>
&lt;tantek> ... to set the min content to zero to act like replaced elements<br>
&lt;tantek> ... seems like useful behavior to get the regular size normally but when you shrink the window you can shrink the element with it<br>
&lt;tantek> ... that's my case for it<br>
&lt;tantek> fantasai: proposed resolution: define a property to switch between these behaviors and hope someone comes up with sensible keywords<br>
&lt;tantek> Rossen_: better than the ones currently in the issue<br>
&lt;tantek> jensimmons: I also think this is a really good idea<br>
&lt;tantek> ... I can see... it's sort of an advanced feature ... authors need to wrap their heads around sizing period. it requires understanding how layout works first.<br>
&lt;tantek> ... to me the big use-case is you have multiple grid items in a grid track, and the track itself is going to be based on something in the track, and you can say don't base it on the headline, base it on something else<br>
&lt;tantek> ... you set its intrinsic size to 0 or 100px<br>
&lt;tantek> ... that could be very powerful<br>
&lt;tantek> ... the columns will be the size of the content in it, except not this content or this content<br>
&lt;tantek> Rossen_: thank you. other opinions or objections to adopting such a property. name and value names tbd<br>
&lt;tantek> ... i see some nodding of heads<br>
&lt;tantek> ... no objections<br>
&lt;tantek> Rossen_: RESOLVED: Adopt a property to solve the requested property and values from issue 4585<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4585#issuecomment-713176382 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 20 October 2020 22:28:27 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:20 UTC