W3C home > Mailing lists > Public > www-style@w3.org > June 2016

[css-containment] Splitting size into width and height

From: Martin Auswöger <martin@auswoeger.com>
Date: Sat, 18 Jun 2016 18:12:21 +0200
To: www-style@w3.org
Message-Id: <A89BFBFF-5A7F-46FF-BA81-2E81BD54DA7E@auswoeger.com>

the current CSS containment draft defines the “size containment” and mentions, as a possible use case, JS libraries implementing the “container query” concept. I wrote [such a library][1] and think it would be very helpful if size containment could be enabled for one dimension only so that the other dimension can still be auto-sized.

Tab Atkins already wrote something about this here on [16 Mar 2016][2]
> It's also useful for userland implementations of "container queries" to prevent loops, especially if we can activate it *solely* for the inline axis (letting the block axis still auto-size based on children).

There was also a discussion about container queries and size containment at [ResponsiveImagesCG/container-queries#3][3].

Containment could get changed to:

contain: none | strict | content | [ layout || style || paint || [ size | [ width || height ] ] ]

There may be better names for width/height like size-x/size-y or inline-size/block-size but I think width/height ist more obvious for CSS authors.

Does this make sense, or could it have any negative implications?


[1]: https://github.com/ausi/cq-prolyfill
[2]: https://lists.w3.org/Archives/Public/www-style/2016Mar/0245.html
[3]: https://github.com/ResponsiveImagesCG/container-queries/issues/3#issuecomment-185951645
Received on Monday, 20 June 2016 07:46:43 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:03 UTC