- From: mattwoodrow via GitHub <sysbot+gh@w3.org>
- Date: Mon, 23 Sep 2019 09:58:45 +0000
- To: public-css-archive@w3.org
> > Overflow:scroll shouldn't create a pseudo stacking context (unfortunately), since it should be possible for things outside the scroller to interleave things inside. That'd be a significant webcompat change I think. > > Pseudo stacking contexts aren't stacking contexts. They are just paint-as-if-positioned, plus the relationship to backface-visibility and maybe preserve-3d. > > As for web compat: Blink already does it, so it's web compatible. And I do think that it is likely not good that backface-visibility leaks across scrolling elements. Oh interesting, I wasn't aware that Blink/WebKit were doing that. Made a quick testcase to display the difference: https://codepen.io/woodrow_matt/pen/jONXjNG I think overflow:scroll isn't painting as positioned, since the red (actually positioned) is still on top. It's definitely causing the background (blue) and content (image) to form a group and not get the orange floated color between them though. It feels a bit weird to have overflow:hidden and overflow:scroll result in different paint orders. Anyway, we should probably do that as a separate change if you want to try spec it, since it's a definite behaviour change for Gecko. -- GitHub Notification of comment by mattwoodrow Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4360#issuecomment-534034030 using your GitHub account
Received on Monday, 23 September 2019 09:58:46 UTC