- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 29 Aug 2018 00:11:13 +0000
- To: public-css-archive@w3.org
frivoal has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-contain] Position in painting order == layout and paint containment cause the element to establish a stacking context. Where in the painting order does that go? I believe the normative description for this is https://www.w3.org/TR/CSS22/zindex.html, and that seems to say that the element stays wherever it would otherwise be: just becoming a stacking context doesn't change its place in the painting order, it only affects the painting order of its descendants. However, I believe that that was written when the only thing that could create stacking contexts was positioned elements, so there may be some shortcuts taken in that description, and maybe the intent would be that all things which create a stacking context, including elements with containment, get the same position in painting order as if they were positioned elements with z-index: auto. I don't think I understand stacking contexts well enough to answer than myself. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3063 using your GitHub account
Received on Wednesday, 29 August 2018 00:11:14 UTC