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
Description of the bug
The Scrollspy breaks when loading a page with an anchor. Since using an anchor as for example by clicking on the scrollspy on an already loaded page does not reload the page and therefore does not produce the bug this behavior is uncommon to detect I guess.
Scrolling inside the Scrollspy related element shows the anchor position is now wrongly considered to be the top of the page (e.g. section 1 is highlighted instead of section 3 when landing on the page and if scrolling to the top nothing is highlighted instead of section 1).
Expected behavior
Loading the page with an anchor should not affect the Scrollspy offset.
Actual behavior
Loading the page with an anchor creates an offset for the Scrollspy
The text was updated successfully, but these errors were encountered:
Landing on the page with an anchor is now fixed. However reloading the page after having scolled the bar still creates the offset. You can replicate this by going to the scrollspy scroll to the bottom within the window with the scrollspy and then reload the page. The scroll state will keep the same (e.g. remain at the bottom) but the scrollspy will reset to top position.
Does one create a new issue for this or could we reopen this one if this is an issue worth investigating? (I am new to this.)
Description of the bug
The Scrollspy breaks when loading a page with an anchor. Since using an anchor as for example by clicking on the scrollspy on an already loaded page does not reload the page and therefore does not produce the bug this behavior is uncommon to detect I guess.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Loading the page with an anchor should not affect the Scrollspy offset.
Actual behavior
Loading the page with an anchor creates an offset for the Scrollspy
The text was updated successfully, but these errors were encountered: