You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 24, 2018. It is now read-only.
Isee 3 open issues all discussing errors with hash navigation on page load, but they don't seem to specifically site the data-menu-offset being ignored on the initial scroll when you arrive at a page with a hash in the navigation.
I have a website using skrollr with a 60px fixed header, so use data-menu-offset="-60" on each of my content panels. My navigation links work just fine when clicking after the page has loaded, but if you arrive at the page with a hash in the URL, skrollr kicks in and scrolls to the top of that DIV, but ignores the offset. Seems like maybe it's initiating too early or just ignoring that property on init()..
Apologies if this has been covered already - I scrolled through open and closed issues and couldn't find it described quite like this.
Cheers
The text was updated successfully, but these errors were encountered:
(It occurred to me that the error being thrown by skrollr that's described in Issues #8 and #12 may be responsible for this problem, and that actually what I'm seeing is just the default browser behaviour (i.e. the hash in the URL leads the page to knock down to the DIV with that ID, obviously ignoring the offset).)
Hi,
Isee 3 open issues all discussing errors with hash navigation on page load, but they don't seem to specifically site the data-menu-offset being ignored on the initial scroll when you arrive at a page with a hash in the navigation.
I have a website using skrollr with a 60px fixed header, so use data-menu-offset="-60" on each of my content panels. My navigation links work just fine when clicking after the page has loaded, but if you arrive at the page with a hash in the URL, skrollr kicks in and scrolls to the top of that DIV, but ignores the offset. Seems like maybe it's initiating too early or just ignoring that property on init()..
Apologies if this has been covered already - I scrolled through open and closed issues and couldn't find it described quite like this.
Cheers
The text was updated successfully, but these errors were encountered: