Re: [csswg-drafts] [css-position][css-sticky] Should overflowing sticky element continue scrolling until meeting opposite offset? (#2558)

@smfr @hober Can you provide any examples that show how the current behavior shows a natural feeling? You are the first to share this view with me after asking many folks about the current behavior. See the current use of `position: sticky` on the `aside.metadata-container` in chromiums bug tracker and see how natural it feels when trying to reach the end of the aside to say click on the "View details" link?

- https://bugs.chromium.org/p/chromium/issues/detail?id=497851


@SebastianZ AFAICT what you are describing is something above and beyond sticky, and more akin to the chromium devs search for "hidey bar" solutions better achieved through houdini mechanisms?

- https://github.com/w3c/css-houdini-drafts/blob/master/scroll-customization-api/UseCases.md#hidey-bars
- https://github.com/w3c/css-houdini-drafts/blob/master/scroll-customization-api/UseCases.md#re-targeting-scrolling
- https://www.webcomponents.org/element/@polymer/app-layout/elements/app-header

I personally like to think of that as more "swinging" behavior, and though a "hidey bar" is most thought of as a nav bar that doesn't in fact overflow it's scrolling context, the swinging behavior is the same where scroll direction is "retargeted" to the placement of this "sticky" element between its constrained (overflowing) edges.

But concerning the current spec language, I am fairly certain it was never written with overflowing sticky elements in mind and what we have is just what has emerged, not providing very much utility. The original example linked in this issue shows it quite well, aside from hidey/swinging behavior which I'm guessing is beyond the scope of the sticky position scheme since it needs scroll direction latching.

PS We need a new css-position editor. :(

-- 
GitHub Notification of comment by jonjohnjohnson
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2558#issuecomment-486878654 using your GitHub account

Received on Thursday, 25 April 2019 23:59:09 UTC