- From: SelenIT via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Feb 2018 20:43:24 +0000
- To: public-css-archive@w3.org
@Nadya678, as far as I understand, the CSS2.x spec had to change the definition of the `position:fixed` effect on the stacking context (at some point in 2015, see [errata for CSS2.1](https://www.w3.org/Style/css2-updates/REC-CSS2-20110607-errata.html#s.9.9.1) and the "Changes" section in CSS2.2) in order to match the reality better. WebKit/Blink browsers had implemented it this way in 2012 (for mobile performance reasons) and other browsers had to follow because of interoperability. The MDN's warning also refers only to the current reality (the fact that most mobile browsers are either WebKit/Blink-based or those that copied the same behavior, while on desktops there are browsers with different behavior like Edge). It doesn't prescribe anything for new browser. And I agree with @Loirooriol and @tabatkins that per current CSS Position Level 3 draft `position:sticky` with `z-index:auto` shouldn't create new stacking context (although, unfortunately, this spec is still marked with "Not ready for implementation" banner). -- GitHub Notification of comment by SelenIT Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2326#issuecomment-367112616 using your GitHub account
Received on Tuesday, 20 February 2018 20:43:26 UTC