- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 02 Aug 2022 14:41:40 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Clarify how c-i-s affects size containment aglo`, and agreed to the following: * `RESOLVED: contain-intrinsic-size size is used as the natural sizes of replaced elements (but does not set the aspect ratio)` <details><summary>The full IRC log of that discussion</summary> <fantasai> Subtopic: Clarify how c-i-s affects size containment aglo<br> <fantasai> s/aglo/algo/<br> <fantasai> github: https://github.com/w3c/csswg-drafts/issues/7519<br> <fantasai> oriol: There's a bunch of sentences in the spec, mostly editorial, but the interaction of how the algo in containment spec is altered to take c-i-s into account<br> <fantasai> oriol: mostly editorial, might not worth it to discuss now, just one thing I wanted to discuss is<br> <fantasai> oriol: what about replaced elements?<br> <fantasai> oriol: The contain spec sais that when you have a replaced element with size containment, it behaves as if it had no natural size<br> <fantasai> oriol: and the natural size was zero<br> <fantasai> oriol: what happens if you have c-i-s?<br> <fantasai> oriol: what Chromium does is that the replaced element still doesn't have a natural size<br> <fantasai> oriol: but the natural width and height are the ones specified in c-i-s<br> <fantasai> oriol: does this make sense, or do we want some other behavior?<br> <fantasai> TabAtkins: having natural width/height take from c-i-s makes sense<br> <fantasai> s/had no natural size/had no natural aspect ratio/<br> <fantasai> s/have a natural size/have a natural aspect ratio/<br> <fantasai> TabAtkins: you asked, why do first layout if going to relayout<br> <fantasai> TabAtkins: answer is, we want to make sure that under normal circumstances, width calculates before height<br> <fantasai> TabAtkins: depending on contents, can have different effets<br> <fantasai> TabAtkins: once have width, then calculate height<br> <fantasai> oriol: so can we have an example of these cases in the spec?<br> <fantasai> ACTION TabAtkins add an example<br> <fantasai> ACTION: TabAtkins add an example<br> <fantasai> Rossen_: does that mean we don't need to change anything?<br> <fantasai> TabAtkins: Oriol's second example, needs fixing in the spec<br> <Rossen_> q?<br> <emilio> fantasai: we want to clarify that it doesn't set the a-r right?<br> <fantasai> Proposed: contain-intrinsic-size size is used as the natural sizes of replaced elements (but does not set the aspect ratio)<br> <iank_> some SVGs have this behaviour.<br> <emilio> TabAtkins: yeah<br> <emilio> fantasai: I wanna suggest that if the aspect-ratio...<br> <emilio> TabAtkins: we wanna say that it doesn't have an intrinsic aspect-ratio, the property can affect<br> <emilio> fantasai: wonder if there's utility in being able to set the a-r from those sizes<br> <emilio> ... guess it has to be opt-in, we don't know if the element is supposed to have an aspect-ratio<br> <iank_> if you want to opt-in to an aspect-ratio you can just set the aspect-ratio as well?<br> <emilio> ... we might want to have that ability<br> <emilio> ... yeah, you can do that explicitly, but it'd be easier to have it computed from c-i-s<br> <emilio> ... that's something to think about but can be addressed later<br> <emilio> Rossen_: objections?<br> <fantasai> RESOLVED: contain-intrinsic-size size is used as the natural sizes of replaced elements (but does not set the aspect ratio)<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7519#issuecomment-1202721367 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 2 August 2022 14:41:42 UTC