Closed Dariusvne closed 1 week ago
Do you see the same at https://dev.mudblazor.com?
cc @epithet
The https://github.com/MudBlazor/MudBlazor/pull/8711 fixed it Tho you never can activate the first item even if it's clicked.
The #8711 fixed it Tho you never can activate the first item even if it's clicked.
@ScarletKuro The first item can be activated if the first section is big enough that it can be activated by scrolling to it. It's like this because the section nearest to the middle of the page is activated. This could be changed in several ways:
In any case, I personally don't see a way to fix the previous behavior
I'm closing this, as it was fixed in v7.
Bug type
Component, Docs (mudblazor.com)
Component name
MudPageContentNavigation
What happened?
In the image above the bug is visible, the page is way past the api section but the nav menu is left behind.
Expected behavior
The nav menu does not stop working after clicking on the first element.
Reproduction link
No need, it is clearly visible within the docs
Reproduction steps
Relevant log output
No response
Version (bug)
6.19.1
Version (working)
No response
What browsers are you seeing the problem on?
Chrome
On which operating systems are you experiencing the issue?
Windows
Pull Request
Code of Conduct