sticky-react
v1.0.1
Published
ReactJS sticky component
Maintainers
Readme
sticky-react
react-sticky + typescript + react 17+
📖 Docs
react-sticky
Make your React components sticky!
Update No longer actively maintained:
The 6.0.3 release is the last release maintained. This means we will not be considering any PR's and/or responding to any issues until a new maintainer is identified. It is highly recommended that you begin transitioning to another sticky library to ensure better support and sustainability. This is obviously less than ideal - sorry for any inconvenience!
Demos
Version 6.x Highlights
- Completely redesigned to support sticky behavior via higher-order component, giving you ultimate control of implementation details
- Features a minimal yet efficient API
- Drops support for versions of React < 15.3. If you are using an earlier version of React, continue to use the 5.x series
CSS
There's a CSS alternative to
react-sticky: theposition: stickyfeature. However it currently does not have full browser support, specifically a lack of IE11 support and some bugs with table elements. Before usingreact-sticky, check to see if the browser support and restrictions prevent you from usingposition: sticky, as CSS will always be faster and more durable than a JS implementation.position: -webkit-sticky; position: sticky; top: 0;Installation
npm install react-stickyOverview & Basic Example
The goal of
react-stickyis make it easier for developers to build UIs that have sticky elements. Some examples include a sticky navbar, or a two-column layout where the left side sticks while the right side scrolls.
react-stickyworks by calculating the position of a<Sticky>component relative to a<StickyContainer>component. If it would be outside the viewport, the styles required to affix it to the top of the screen are passed as an argument to a render callback, a function passed as a child.<StickyContainer> <Sticky>{({ style }) => <h1 style={style}>Sticky element</h1>}</Sticky> </StickyContainer>The majority of use cases will only need the style to pass to the DOM, but some other properties are passed for advanced use cases:
style(object) - modifiable style attributes to optionally be passed to the element returned by this function. For many uses, this will be the only attribute needed.isSticky(boolean) - is the element sticky as a result of the current event?wasSticky(boolean) - was the element sticky prior to the current event?distanceFromTop(number) - number of pixels from the top of theStickyto the nearestStickyContainer's topdistanceFromBottom(number) - number of pixels from the bottom of theStickyto the nearestStickyContainer's bottomcalculatedHeight(number) - height of the element returned by this functionThe
Sticky's child function will be called when events occur in the parentStickyContainer, and will serve as the callback to apply your own logic and customizations, with sanestyleattributes to get you up and running quickly.Full Example
Here's an example of all of those pieces together:
app.js
import React from 'react'; import { StickyContainer, Sticky } from 'react-sticky'; // ... class App extends React.Component { render() { return ( <StickyContainer> {/* Other elements can be in between `StickyContainer` and `Sticky`, but certain styles can break the positioning logic used. */} <Sticky> {({ style, // the following are also available but unused in this example isSticky, wasSticky, distanceFromTop, distanceFromBottom, calculatedHeight }) => ( <header style={style}> {/* ... */} </header> )} </Sticky> {/* ... */} </StickyContainer> ); }, };When the "stickiness" becomes activated, the arguments to the sticky function are modified. Similarly, when deactivated, the arguments will update accordingly.
<StickyContainer />Props
<StickyContainer />supports all valid<div />props.
<Sticky />Propsrelative (default: false)
Set
relativetotrueif the<Sticky />element will be rendered within an overflowing<StickyContainer />(e.g.style={{ overflowY: 'auto' }}) and you want the<Sticky />behavior to react to events only within that container.When in
relativemode,windowevents will not trigger sticky state changes. Only scrolling within the nearestStickyContainercan trigger sticky state changes.topOffset (default: 0)
Sticky state will be triggered when the top of the element is
topOffsetpixels from the top of the closest<StickyContainer />. Positive numbers give the impression of a lazy sticky state, whereas negative numbers are more eager in their attachment.app.js
<StickyContainer> ... <Sticky topOffset={80}> { props => (...) } </Sticky> ... </StickyContainer>The above would result in an element that becomes sticky once its top is greater than or equal to 80px away from the top of the
<StickyContainer />.bottomOffset (default: 0)
Sticky state will be triggered when the bottom of the element is
bottomOffsetpixels from the bottom of the closest<StickyContainer />.app.js
<StickyContainer> ... <Sticky bottomOffset={80}> { props => (...) } </Sticky> ... </StickyContainer>The above would result in an element that ceases to be sticky once its bottom is 80px away from the bottom of the
<StickyContainer />.disableCompensation (default: false)
Set
disableCompensationtotrueif you do not want your<Sticky />to apply padding to a hidden placeholder<div />to correct "jumpiness" as attachment changes fromposition:fixedand back.app.js
<StickyContainer> ... <Sticky disableCompensation> { props => (...) } </Sticky> ... </StickyContainer>disableHardwareAcceleration (default: false)
When
disableHardwareAccelerationis set totrue, the<Sticky />element will not use hardware acceleration (e.g.transform: translateZ(0)). This setting is not recommended as it negatively impacts the mobile experience, and can usually be avoided by improving the structure of your DOM.app.js
<StickyContainer> ... <Sticky disableHardwareAcceleration> { props => (...) } </Sticky> ... </StickyContainer>FAQ
I get errors while using React.Fragments
React.Fragments does not correspond to an actual DOM node, so
react-stickycan not calculate its position. Because of this, React.Fragments is not supported.
