Security News
Input Validation Vulnerabilities Dominate MITRE's 2024 CWE Top 25 List
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
react-stickynode
Advanced tools
A performant and comprehensive React sticky component.
A sticky component wraps a sticky target and keeps the target in the viewport as the user scrolls the page. Most sticky components handle the case where the sticky target is shorter than the viewport, but not the case where a sticky target is taller than the viewport. The reason is that the expected behavior and implementation is much more complicated.
react-stickynode
handles not only regular case but the long sticky target case in a natural way. In the regular case, when scrolling the page down, react-stickynode
will stick to the top of the viewport. But in the case of a taller sticky target, it will scroll along with the page until its bottom reaches the bottom of the viewport. In other words, it looks like the bottom of viewport pulls the bottom of a sticky target down when scrolling the page down. On the other hand, when scrolling the page up, the top of viewport pulls the top of a sticky target up.
This behavior gives the content in a tall sticky target more chance to be shown. This is especially good for the case where many ADs are in the right rail.
Another highlight is that react-stickynode
can handle the case where a sticky target uses percentage as its width unit. For a responsive designed page, it is especially useful.
scrollTop
only once for all sticky components.The sticky uses Modernizr csstransforms3d
and prefixed
(link) features to detect IE8/9, so it can downgrade not to use transform3d.
import Sticky from 'react-stickynode';
<Sticky enabled={true} top={50} bottomBoundary={1200}>
<YourComponent/>
</Sticky>
import Sticky from 'react-stickynode';
<Sticky top='#header' bottomBoundary='#content'>
<YourComponent/>
</Sticky>
Name | Type | Note |
---|---|---|
enabled | Boolean | The switch to enable or disable Sticky (true by default). |
top | Number/String | The offset from the top of window where the top of the element will be when sticky state is triggered (0 by default). If it is a selector to a target (via querySelector() ), the offset will be the height of the target. |
bottomBoundary | Number/String | The offset from the top of document which release state will be triggered when the bottom of the element reaches at. If it is a selector to a target (via querySelector() ), the offset will be the bottom of the target. |
innerZ | Number/String | z-index of the sticky. |
enableTransforms | Boolean | Enable the use of CSS3 transforms (true by default). |
activeClass | String | Class name to be applied to the element when the sticky state is active (active by default). |
innerClass | String | Class name to be applied to the inner element ('' by default). |
innerActiveClass | String | Class name to be applied to the inner element when the sticky state is active ('' by default). |
className | String | Class name to be applied to the element independent of the sticky state. |
releasedClass | String | Class name to be applied to the element when the sticky state is released (released by default). |
onStateChange | Function | Callback for when the sticky state changes. See below. |
shouldFreeze | Function | Callback to indicate when the sticky plugin should freeze position and ignore scroll/resize events. See below. |
You can be notified when the state of the sticky component changes by passing a callback to the onStateChange
prop. The callback will receive an object in the format {status: CURRENT_STATUS}
, with CURRENT_STATUS
being an integer representing the status:
Value | Name | Note |
---|---|---|
0 | STATUS_ORIGINAL | The default status, located at the original position. |
1 | STATUS_RELEASED | The released status, located at somewhere on document, but not default one. |
2 | STATUS_FIXED | The sticky status, located fixed to the top or the bottom of screen. |
You can access the statuses as static constants to use for comparison.
import Sticky from 'react-stickynode';
const handleStateChange = (status) => {
if (status.status === Sticky.STATUS_FIXED) {
console.log('the component is sticky');
}
}
<Sticky onStateChange={handleStateChange}>
<YourComponent/>
</Sticky>
Also Sticky
supports children functions:
import Sticky from 'react-stickynode';
<Sticky>
{status => {
if (status.status === Sticky.STATUS_FIXED) {
return 'the component is sticky';
}
if (status.status === Sticky.STATUS_ORIGINAL) {
return 'the component in the original position';
}
return 'the component is released'
}}
</Sticky>
You can provide a function in the shouldFreeze
prop which will tell the component to temporarily stop updating during prop and state changes, as well as ignore scroll and resize events. This function should return a boolean indicating whether the component should currently be frozen.
Install
npm install react-stickynode
Unit Test
npm run test
Linting
npm run lint
This software is free to use under the BSD license. See the LICENSE file for license text and copyright information.
FAQs
A performant and comprehensive React sticky component
We found that react-stickynode demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 5 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
MITRE's 2024 CWE Top 25 highlights critical software vulnerabilities like XSS, SQL Injection, and CSRF, reflecting shifts due to a refined ranking methodology.
Security News
In this segment of the Risky Business podcast, Feross Aboukhadijeh and Patrick Gray discuss the challenges of tracking malware discovered in open source softare.
Research
Security News
A threat actor's playbook for exploiting the npm ecosystem was exposed on the dark web, detailing how to build a blockchain-powered botnet.