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
Suggest you change it to event blazor and make @attribute. Why? Many people who modify the template get rid of this component by putting the navigation in MainLayout. Unfortunately, Layout is not dynamic by which interactivity does not work. I caught myself in this trap.
Other people also had similar problems #50712#50724
For the WebAssembly template, I would put the navigation in Client and do the rendering on the client side. This will be the best example for newbies. Also, in MainLayout you can comment out the link to the documentation that tells us that server-side rendering doesn't work.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Is your feature request related to a problem? Please describe the problem.
Currently, the default blazor template for navigation uses javascript:
Suggest you change it to event blazor and make
@attribute
. Why? Many people who modify the template get rid of this component by putting the navigation in MainLayout. Unfortunately, Layout is not dynamic by which interactivity does not work. I caught myself in this trap.Other people also had similar problems #50712 #50724
For the WebAssembly template, I would put the navigation in Client and do the rendering on the client side. This will be the best example for newbies. Also, in MainLayout you can comment out the link to the documentation that tells us that server-side rendering doesn't work.
The text was updated successfully, but these errors were encountered: