- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Mon, 28 Aug 2023 18:37:08 +0000
- To: public-css-archive@w3.org
nt1m has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-contain] What should container font relative units match against by default? == #8855 resolved on adding new container-font relative units, however it's not clear which container they should query against. cqw & cqh can match against different containers depending on the container type (inline-size vs. size). Some options are: - nearest named container: useful by default, drawback would be the inconsistency with cqw/cqh (which may be confusing if you are using them in an un-named `@container` at-rule) - style containers: this makes sense, and is somewhat consistent with cqw/cqh, drawback is that this would always be the parent element, so the units would be useless without the notation from #7858 - inline-size containers: would be somewhat consistent with the majority of the cqw cases, but not really obvious behavior. - adding a new font container-type - only allowing those units with the notation from #7858, although having to always specify a container name might be extra-verbose. cc @mirisuzanne @tabatkins @fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9255 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 28 August 2023 18:37:10 UTC