Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RadzenPanelMenuItem does not respect/override Match NavLinkMatch.All #1661

Closed
xXBuilderBXx opened this issue Aug 20, 2024 · 1 comment · Fixed by #1662
Closed

RadzenPanelMenuItem does not respect/override Match NavLinkMatch.All #1661

xXBuilderBXx opened this issue Aug 20, 2024 · 1 comment · Fixed by #1662

Comments

@xXBuilderBXx
Copy link

xXBuilderBXx commented Aug 20, 2024

Describe the bug
RadzenPanelMenuItem does not respect Match NavLinkMatch.All unless you set the main RadzenPanelMenu to NavLinkMatch.All which seems like it should override it?
Using latest version 5.1.1

To Reproduce
Steps to reproduce the behavior:

  1. Create a menu item with.
<RadzenPanelMenu>
    <RadzenPanelMenuItem Path="/test" Match="NavLinkMatch.All" Text="Test Page" />
</RadzenPanelMenu>
  1. Load a page with the path /test/website /test/name ( Not /test )
  2. Menu item seems to be showing as active when it should not be.

Expected behavior
The nav link should only match All of the path which is /test

Weird Fix
In theory PanelMenuItem should be overriding the main PanelMenu for matching but looks like setting Match="NavLinkMatch.All" on PanelMenu sort of fixes this issue but not sure if NavLinkMatch.Prefix will work on PanelMenuItem.

<RadzenPanelMenu Match="NavLinkMatch.All">
    <RadzenPanelMenuItem Path="/test" Match="NavLinkMatch.All" Text="Test Page" />
</RadzenPanelMenu>
@enchev
Copy link
Collaborator

enchev commented Aug 20, 2024

I've just submitted pull request with a change related to this issue. Let me know if this is what you are looking for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants