- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Sat, 13 Oct 2018 05:02:53 +0000
- To: public-css-archive@w3.org
Chromium already treats both position: fixed and position: sticky as stacking contexts. See [here](https://cs.chromium.org/chromium/src/third_party/blink/renderer/core/style/computed_style.cc?q=computed_style.cc&sq=package:chromium&dr&l=932). The reason that such elements are stacking contexts is that they need to move with respect to scroll, and in particular composited scrolling layers. Therefore they are put in their own composited layer, and if that layer were *not* a stacking context, then a lot of unnecessary implementation complexity would result due to the contents of the fixed/sticky subtree not being atomically rendered. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1053#issuecomment-429511668 using your GitHub account
Received on Saturday, 13 October 2018 05:02:54 UTC