- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 31 Mar 2022 15:25:27 +0000
- To: public-css-archive@w3.org
contain-intrinsic-size should have no direct interaction with this object-view-box; the two are operating on different concepts and at different "times", so they'll each just do their own thing. In particular, c-i-s sets the "explicit intrinsic inner size", which is a term of art defined to have an effect on how a contain:paint element is sized (it overrides the results of calculating the size of the element's content); this is unrelated to the natural sizes of a replaced element, which are derived directly from the image/etc. o-v-b just changes how the image content itself reports its natural sizes and paints itself relative to those natural-size bounds; layout of the image into whatever layout-based sizes you get happen after that. As far as all of layout is concerned, you've just loaded an image whose natural dimensions are now what o-v-b reports, and which might paint slightly oddly (outside the bounds of those natural sizes); in all other respects it's identical to how the image would have originally worked without o-v-b. The fact that these questions are coming up at all, tho, indicates that I almost certainly *do* need to go ahead and define some more terms to make this layering more explicit; I was trying to avoid that. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7187#issuecomment-1084744745 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 31 March 2022 15:25:29 UTC