- From: Martin Robinson via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Jun 2022 13:35:51 +0000
- To: public-css-archive@w3.org
mrobinson has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-contain] Clarify what happens when `display: contents` and `contain: style` are used together == Regarding https://drafts.csswg.org/css-contain/#containment-style: The other types of containment have language like this: > If the element does not generate a [principal box](https://www.w3.org/TR/css-display-3/#principal-box) (as is the case with [display](https://www.w3.org/TR/css-display-3/#propdef-display) values of [contents](https://www.w3.org/TR/css-display-3/#valdef-display-contents) or [none](https://www.w3.org/TR/css-display-3/#valdef-display-none)), or its principal box is an [internal table box](https://www.w3.org/TR/css-display-3/#internal-table-box) other than [table-cell](https://www.w3.org/TR/css-display-3/#valdef-display-table-cell), or an [internal ruby box](https://www.w3.org/TR/css-display-3/#internal-ruby-box), or a [non-atomic](https://www.w3.org/TR/css-display-3/#atomic-inline) [inline-level](https://www.w3.org/TR/css-display-3/#inline-level) box, paint containment has no effect. This means these types of containment have no affect when `display: contents` is used. In the case of `contain: style` this text isn't there. Should elements that have `contain: style` and `display: contents` establish a new style boundary? It seems that in Chrome it does, though perhaps with some bugs. In Gecko, this behavior might be a bit trickier to implement. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7392 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 20 June 2022 13:35:53 UTC