-
-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Request: Sticky navbar affixed to container on scroll #49
Comments
Thank you for your suggestion and detailed issue. I'll look at getting this implemented in a future version. |
Feature added in master will be included in the next release. |
Thank you! |
Could you point me in the direction of a working implementation of this? |
Hey @networkchimp, The BulmsJS's documentation navbar uses the sticky feature, without the auto-hiding etc. The docs can be found at https://bulmajs.tomerbe.co.uk/docs/0.10/2-core-components/navbar/ |
Is your feature request related to a problem? Please describe.
Following the introduction of the Fixed Navbar feature by issue #326, would it be possible to include a sticky navbar which affixes to the top/bottom of its container upon reaching a certain scroll threshold? Optionally, it could be expanded upon to hide the navbar on scroll down and reveal upon scrolling up?
Describe the solution you'd like
It's a few years out-of-date... which works to our benefit since the adoption of
position: sticky
has increased significantly (CanIUse) across a number of browsers since then.Describe alternatives you've considered
Nav bar sticks to the top of the viewport on both desktop and mobile devices alike.
A more granular breakdown and demonstration of the sticky navbar behaviour.
Admittedly, this is a script but the implementation of the "smart" sticky navbar is very smooth and would be ideal to target, if at all possible. More than happy for this to be offloaded to a separate issue/request if that makes feature management easier.
Thanks for your time and I really appreciate your suggestion to create this ticket from the original issue #2051. Hope you have a great day!
The text was updated successfully, but these errors were encountered: