-
Notifications
You must be signed in to change notification settings - Fork 152
elements disappear from view, rather than scroll out of view #28
Comments
Yeah, this is a known issue, currently listed as |
here's a different query plugin where I'm doing that type of work already. it now does some sticky polyfilling, behind the other work it does managing display based on size of a column's content, and other special behavioral tests that one of my sites needed. i ended up just using negative top w/ fixed positioning to scroll the element off screen. absolute/bottom would save some need to content related measurements, but for this case I was already doing them all. |
Alright, this should be working in the issue-28 branch. Have a look, I’ll leave it here for a bit and think over the weight/benefit of the feature. |
+1 This was exactly what I needed. I hope to see this also in the master branch. |
This is a blocking issue for most of my use cases. The code in the
|
+1 |
@zachleat any idea of when we will see this merged? |
This is still an issue for me. It's disappearing at the bottom of my containing element in chrome 55 on OS X. My sticky element is tall-ish (height:651px;). @zachleat Is there a workaround I can use in the meantime? I'm happy to try and make a PR if need be. |
Looking at the demo (as well as my own test implementation) with Chrome 35 OS X, when an element switches from .fixedsticky-on to .fixedsticky-off it just out of view, but in sticky supporting environments it will be stuck to the bottom of the container and scroll out of view.
This jump is particularly jarring with taller elements (for example, a sticky sidebar rather than the short demo header), a behavior I can't have this happen in my particular project.
Example: scroll down in the demo watch the behavior of the red "Fixed to viewport top A." banner (#top-a) in demo when the first grey .container begins to leave view.
Potential Solution: Perhaps rather than using the "off" mode, having an "end" mode, setting position:absolute; bottom:0 (or calculated top) so the .fixedsticky item doesn't go poof?
The text was updated successfully, but these errors were encountered: