jonjohnjohnson

Just wanted to make a note for others about how allowing general `overflow: hidden` ancestors to not be the "scrolling context" for a sticky element isn't always desirable. When using...

@damienroche I believe androids webview behaves according to spec here, but it's iOS that doesn't. If you want to chip in and voice concern about their noncompliance here's the public...

@valtlai @WangXBruc I don't exactly condone this fix, but if you really need some sort of nested separate scroller with separate axis treatment, this is the best approach yet. https://uxdesign.cc/position-stuck-96c9f55d9526...

@joshjg @JacobDB I provided that link in response to a [case](https://github.com/w3c/csswg-drafts/issues/865#issuecomment-350585274) which is a bit different/more than this filing, so I'd suggest opening up a separate issue. Something along the...

Related... Though `@supports(position:sticky)` currently parses for all major vendors, Blink, which has the largest market share, still doesn't *fully support the value. @SelenIT https://github.com/w3c/csswg-drafts/issues/2155#issuecomment-410978077 > It seems that for some...

Methinks this should have the same solution as [#156 - CSS Snap Points: Event Model Missing](https://github.com/w3c/csswg-drafts/issues/156)