On our site we have a RadzenAutoComplete that we use as a little quick-search for various pages and external links. Users can start typing in the box for what they are looking for, and then results appear as links that they can click to open a new tab. This functionality is broken/buggy now.
We noticed some odd behavior with our site where a tab would get into some sort of a broken state, and would have some weird behavior. Any links that were pressed (either anchor tags or RadzenLinks) would get run a bunch of times per user click, increasing in number over time and eventually clicking on a link would open over ten tabs if targeting _blank. There are also other odd behaviors surrounding the bugged state like how right-clicking on links starts navigation rather than opening the browser's context menu, and some weirdness with the history entries in the browser if not using _blank.
We tracked the issue to the RadzenAutoComplete on the page. Specifically occurring after This GitHub Commit. To reproduce (using the AutoComplete Template demo):
-
Make sure the "Define AutoComplete template" demo is centered on your screen, and don't scroll around the page while replicating this. The way the demo site handles the subheading navigation (like #template) breaks the example if it keeps changing due to scrolling and resizing.
-
Change the template of the component to have a link in it, these links will be the ones that cause the bugged state. Something like this:
<Template>
<a href="https://www.google.com/search?q=@(context.Country)" target="_blank">@(context.Country)</a>
</Template>
- Then put a second link at the bottom of the html, this link will be the one that can be right-clicked, and gets opened multiple times in your browser:
<RadzenLink Path="https://www.google.com" Target="_blank" Text="test" />
- Now, to get it in a bugged state just click the links in the AutoComplete a few times as if you were following a few of them to interesting places. You will know it is in the bugged state when right-clicking on the "test" link opens a new tab instead of the context menu, and if you clicked enough links in the AutoComplete it will open multiple tabs of the test link.
The recent release of Radzen Blazor 7.0 seems to have little-to-no effect on this bug. I would have included more detailed info on why the bug is happening, but I don't know enough about the normal operation of your javascript to pin down the issue specifically. I would assume it's an issue with the way the GitHub Commit was implemented, meaning the change should be reverted and a better solution found.
Thanks for your help, let me know if you need any other information or have any questions.