We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What we're after: I'd like to remove the component-sticky package.
None
To test the idea and approach
A. Inspector
:has(> .js-sticky-side) { position: sticky; top: 0px; }
B. Build process
init.js
data-init.js
new Sticky
_nav.scss
npm run build
C. Final code changes
has(> .js-sticky-side)
js-sticky-side
js-
Are there other things we want to be sticky under certain conditions?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Summary
What we're after:
I'd like to remove the component-sticky package.
Related issues
None
Completion criteria
Tech steps or considerations (optional)
To test the idea and approach
A. Inspector
:has(> .js-sticky-side) { position: sticky; top: 0px; }
B. Build process
init.js
anddata-init.js
, comment out thenew Sticky
lines:has(> .js-sticky-side) { position: sticky; top: 0px; }
into scss somewhere._nav.scss
?npm run build
C. Final code changes
new Sticky
functionality lineshas(> .js-sticky-side)
would mean we don't need to adjust other class names anywhere—we can use what we already havejs-sticky-side
would be inconsistent with thejs-
prefixing signifying JavaScript targets since this would be strictly a css approachFuture work
Are there other things we want to be sticky under certain conditions?
The text was updated successfully, but these errors were encountered: