Re: [csswg-drafts] [css-contain] Is it ok that contain:layout is a CB for fixpos/abspos descendants but doesn't establish a stacking context?

The Working Group just discussed `Is it ok that contain:layout is a CB for fixpos/abspos descendants but doesn't establish a stacking context?`, and agreed to the following:

* `RESOLVED: Accept the PR that corrects this oversite`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Is it ok that contain:layout is a CB for fixpos/abspos descendants but doesn't establish a stacking context?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2942<br>
&lt;dael> florian: contain layout sets the element to be a containing block for lots of things, but didn't say it establishes stacking. This would be a first time we would have something liek this that's not stacking, so let's do it<br>
&lt;dael> TabAtkins: And it wasn't intentional, accidental tying concepts and didn't realize<br>
&lt;dael> astearns: Not seeing obj in issue<br>
&lt;dael> astearns: Obj?<br>
&lt;dael> RESOLVED: Accept the PR that corrects this oversite<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2942#issuecomment-409762755 using your GitHub account

Received on Thursday, 2 August 2018 00:00:22 UTC