The default fallback page is always loaded first, even if the browser's address bar indicates other paths.

From: @fingers10
(The original post is in the Issue #2)

---

@jsakamoto , I would like to understand more on flickering effect that occurs when prerendered site is loaded. Please can you assist me on this.

I have this repo - https://github.com/fingers10/WasmServerPrerender published to GitHub Pages using the below URL.

Here is the sample URL that I’m using for testing - https://fingers10.github.io/WasmServerPrerender/fetchdata

Steps I followed,

1. When I load in incognito window in chrome - The flickering effect is minimal. Only Data Shown in the screen is flickering. This is fine.
2. When I load in normal window in chrome - index.html in wwwroot loads and the actual page loads. Is this the expected behavior?
3. When I reload in both normal and in incognito window in chrome - index.html in wwwroot loads and the actual page loads. Is this the expected behavior?

Here is the video showing the same.

https://user-images.githubusercontent.com/43729469/176577418-17ed84df-8dc9-4625-848f-12e15ba563c0.mp4

Thank you for your support and teaching.

[jsakamoto]

Can we report this to Microsoft in aspnet repo?

Yes we can! I posted about this problem to the ASP.NET Core repository right now.

• https://github.com/dotnet/aspnetcore/issues/25731#issuecomment-1183214726

And I also tweeted it.

• https://twitter.com/jsakamoto/status/1547210240395190272

I’ll appreciate it if you vote my issue comment and retweet my tweet above.

[fingers10]

@jsakamoto, Thanks for the inputs and fix. Now the correct page is getting loaded.

The flickering effect is minimal for simple screen - https://fingers10.github.io/WasmServerPrerender/fetchdata

But obvious for the following URL - https://ilovedotnet.org/blogs/blazor-wasm-publishing-to-iis

Here is the sample video.

https://user-images.githubusercontent.com/43729469/178150015-ad04a36b-7a52-41c9-8098-14ac19b42027.mp4