-
Notifications
You must be signed in to change notification settings - Fork 11
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
<Link> creates forece reload #35
Comments
@Alerinos Unfortunately, I could not reproduce the force reloading that you said yet. My sample project is here: Could you take a look at my sample project above? |
I tried to open an issue on the project you submitted. I failed to. Once I noticed that something like this happens when you load static files (pictures, background, more css etc). |
I am currently researching this issue. It still exists. This looks like a similar scenario that is in the documentation. @jsakamoto Can you look at the code again? Maybe you missed something. Thanks! |
@drma-dev Sorry too late since I was busy watching the .NET Conf 2022 that was held this week. (I live in Japan, so I had to wake up at midnight in the Japan Standard Time zone and keep staying up).
Ok, but I don't have the confidence to resolve this issue as far as I've gotten limited information below:
Could you disclose the source code of the app that has the problem we are discussing in this thread? |
Using this method causes a heavy reload of the page:
The problem is described here:
dotnet/aspnetcore#15317
What's the problem?
In the case of server side rendering, blazor loads the page content and then the async elements are reloaded.
This gives us the effect of double page loading.
Only Link has a problem, meta tags work well.
Demo:
https://gyazo.com/b36e3ea01ebeefb56e60b524b3b24532
If I don't use or _headElementHelper.SetLinkElementsAsync then the problem disappears.
The text was updated successfully, but these errors were encountered: