W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2020

[csswg-drafts] [css-contain-2] apply containment on `content-visibility: visible` ; use `normal` as initial value (#5695)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Wed, 04 Nov 2020 23:20:34 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-736487825-1604532033-sysbot+gh@w3.org>
tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-contain-2] apply containment on `content-visibility: visible` ; use `normal` as initial value ==
Currently, `content-visibility` is specified to have three values: `visible`, which does nothing; `hidden`, which hides the element and applies containments; and `auto`, which switched between `hidden` behavior and a visible-with-containments behavior that is otherwise not representable via `content-visibility`.

This seems weird! Particularly with [`hidden-matchable`](), where the author is expected to flip the element into being visible, flipping it to `visible` is probably wrong (you lose the containments, unless you've applied them independently) and flipping it to `auto` feels awkward and, depending on scroll position, might not actually make the element visible.

@fantasai and I think that it would be better to have an explicit value for each of `auto`’s states, calling them `hidden` and `visible`; and to call the initial value, which has no effect on the element, `normal`.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5695 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 4 November 2020 23:20:36 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:22 UTC