- From: danegraphics via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Dec 2023 02:22:40 +0000
- To: public-css-archive@w3.org
> This fails to consider that even if height: auto makes the element be 507px tall, the behavior can be different than with height: 507px. In particular, if a child has a percentage, it will be cyclic for auto, but not for 507px, see https://software.hixie.ch/utilities/js/live-dom-viewer/saved/12246. So how should this child behave during the transition? Thank you for giving an example of what that actually means. The behavior being different despite the sizes of the divs being identical is not something I expected. Honestly, I would consider that to be a bug, either in the browser, or in the spec itself. Identically sized elements with identical children *should* result in identical outcomes, regardless of how those sizes are specified. But since that's not the case, it looks like a work around is indeed necessary unless we're willing to look at fixing that severe inconsistency in the spec. But that would be a new ticket altogether. Perhaps a very worthwhile one. Regardless, I'm still in support of keeping it as simple as possible. --- Perhaps as an alternative to creating a new difficult to intuit function, what of creating an alternative keyword to `auto`? Something that results in identical sizing to `auto` (or as close as possible), however, it's **non-cyclic** and is treated the same as a pixel value would be, and can be transitioned to and from just as any pixel value can be. A keyword like `auto-size` or something? It wouldn't even need to behave identically to `auto`, just be good enough that it can be treated similarly in designs and worked with for transitions. It could even be beneficial for other uses where cyclical problems arising from `auto` might want to be avoided. -- GitHub Notification of comment by danegraphics Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/626#issuecomment-1870762834 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 December 2023 02:22:42 UTC