- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Sat, 14 Oct 2023 22:42:33 +0000
- To: public-css-archive@w3.org
@hfhchan wrote: > I suggest this property be called `intrinsic-size`, and instead of `content` and `fixed`, it should be `none` and `auto`. > > ... > > (For iframe maybe dynamically resizing its height according to content is too difficult to implement and/or introduces security risks. But at least the width should behave like all other display: block elements. Potentially the height should just resolve to 0px as if there were no contents?) > > ... > > (For iframe it may not be feasible to actually resize the width according to its contents. Potentially it should just resolve to 0px as if there were no contents?) > > When `intrinsic-size` is set to `auto`, all the crazy sizing behaviours for img, video, input, select, textarea and iframe are kept as they are currently defined, with img and video sized to their natural width, input, select and textarea to platform defined widths, and iframe to be 300px x 150px, regardless of whether they are block or inline. Resizing iframes based on their contents is discussed in #1771. And it was [resolved on](https://github.com/w3c/csswg-drafts/issues/1771#issuecomment-989034819) adding a `contain-intrinsic-size: from-element`. So that somewhat overlaps with your suggested `intrinsic-size` property. And I wonder whether that should be reused for this use case. In any case, I like the idea of introducing something that covers all the mentioned cases, as they are related. Sebastian -- GitHub Notification of comment by SebastianZ Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7542#issuecomment-1763199634 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 14 October 2023 22:42:35 UTC