- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Jun 2021 17:05:05 +0000
- To: public-css-archive@w3.org
My [big test](https://dbaron.org/css/test/2018/stacking-context-z-order) says that Firefox and Chrome both create a stacking context for `will-change: contain` and it says that Safari doesn't support `contain`. Firefox also makes it a containing block for absolutely- and fixed-positioned elements, and I [recently fixed](https://chromium-review.googlesource.com/c/chromium/src/+/2911476) Chrome to do the same (but it hasn't reached stable yet). Note that the two paragraphs in the spec immediately after the one quoted above are: > If any non-initial value of a property would cause the element to generate a containing block for absolutely positioned elements, specifying that property in will-change must cause the element to generate a containing block for absolutely positioned elements. > > If any non-initial value of a property would cause the element to generate a containing block for fixed positioned elements, specifying that property in will-change must cause the element to generate a containing block for fixed positioned elements. -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6373#issuecomment-857874263 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 June 2021 17:05:50 UTC