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 Sep 16, 2019. It is now read-only.
I am building a one page site, however there a couple of separate pages (eg Posts page, Archives, 404 etc) that I need to link back to the Home page, not an anchor on that particular page. When using a relative URL with the anchor link, the .main-menu li has an .active class applied to it.
How can this bug be reproduced?
Step one
Create a custom relative link in Menus eg. /#style-anchor
Step two
Save Menu
What did you expect to happen?
As expected the link behaves as normal, scrolling to it's respective anchor tag on the homepage, and when on a separate page, links back to the anchor on the homepage
What happened instead?
However, when using a relative URL with the anchor link, the .main-menu li has an .active class applied to it.
Please List the Following:
OS & version: Mac OS El Capitan 10.11.6
Node version (node -v) [Node v4+ is required] : v5.1.1
I am building a one page site, however there a couple of separate pages (eg Posts page, Archives, 404 etc) that I need to link back to the Home page, not an anchor on that particular page. When using a relative URL with the anchor link, the .main-menu li has an .active class applied to it.
How can this bug be reproduced?
Create a custom relative link in Menus eg. /#style-anchor
Save Menu
What did you expect to happen?
As expected the link behaves as normal, scrolling to it's respective anchor tag on the homepage, and when on a separate page, links back to the anchor on the homepage
What happened instead?
However, when using a relative URL with the anchor link, the .main-menu li has an .active class applied to it.
Please List the Following:
Include Test Case (if applicable):
http://bossy2.dylanmcleod.net.au/
I've tried removing all custom JS and deactivating plugins.
The text was updated successfully, but these errors were encountered: