W3C home > Mailing lists > Public > public-css-archive@w3.org > July 2018

Re: [csswg-drafts] [css-transforms-2] Explicitly specify that a transform is a containing block for all descendants

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Tue, 03 Jul 2018 04:48:59 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-402012192-1530593338-sysbot+gh@w3.org>
The Working Group just discussed `Explicitly specify that a transform is a containing block for all descendants`, and agreed to the following:

* `RESOLVED: transform establishes a containing block for all elements.`

<details><summary>The full IRC log of that discussion</summary>
&lt;Rossen> Topic: Explicitly specify that a transform is a containing block for all descendants<br>
&lt;Rossen> github: https://github.com/w3c/csswg-drafts/issues/913<br>
&lt;ericwilligers_> dirk: because of the compositing model of many browsers,  much the same reason as for filter effects<br>
&lt;ericwilligers_> rossen: this means it will also be a containing block for fixed?<br>
&lt;ericwilligers_> rossen: is there interop?<br>
&lt;birtles> dbaron has a test for some of these cases https://dbaron.org/css/test/2018/stacking-context-z-order<br>
&lt;ericwilligers_> ericwilligers: motion path and individual transform properties explicitly create a containing block and stacking context.<br>
&lt;ericwilligers_> rossen: seems like transform in Edge and Chrome and Firefox is considered a containing block.<br>
&lt;ericwilligers_> brian: transform-style flat creates a stacking context in the spec but not implementations.<br>
&lt;ericwilligers_> dirk: some developers don't like the behavior - some want fixed-pos to not create a containing block even if there is a transform.<br>
&lt;ericwilligers_> dbaron: it is a little late to change that.<br>
&lt;ericwilligers_> dbaron: I tried this on 4 engines. Notes at the bottom of test linked above.<br>
&lt;ericwilligers_> dbaron: This is testing many different things. Green means it does the thing, red means it does not.  Sometimes does not correspond to pass/fail.<br>
&lt;ericwilligers_> crossed out means the engine does not implement property.<br>
&lt;ericwilligers_> dirk: confirm WebKit behaves same as Edge and Chrome and Firefox  in creating a containing block.<br>
&lt;ericwilligers_> dirk: will we resolve for filter too?<br>
&lt;ericwilligers_> RESOLVED: transform establishes a containing block for all elements.<br>
&lt;dino> ericwilligers_: Didn't we resolve to add a few options for transform-box?<br>
&lt;dino> ericwilligers_: it's already in the spec<br>
&lt;dino> ericwilligers_: i'm just noting that there have been differences since the most recent publication<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/913#issuecomment-402012192 using your GitHub account
Received on Tuesday, 3 July 2018 04:49:13 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:33 UTC