Skip to content

Server-side Blazor non-interactive after 'back' from external site #10842

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

Closed
SteveSandersonMS opened this issue Jun 4, 2019 · 1 comment
Closed
Assignees
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug.

Comments

@SteveSandersonMS
Copy link
Member

Copied from @chrdlx's report at #10732. I was able to repro this, and don't immediately have any idea why this would happen. Seems like a browser defect, but regardless I think we'd need to find a workaround.


Another related issue with navigation:

Again, default ServerSide Blazor template.
If you go to the "counter" component... make some clicks in the button, then navigate to "microsoft.com" or any website you want... then go back with the browser navigation buttons, the counter component doesn't work anymore until you

  1. Refresh the page F5 or 2) Go to the "fetch data" component and go back to the counter component.

bug2

@SteveSandersonMS
Copy link
Member Author

I investigated, and this only happens when you're doing stateful prerendering with server-side Blazor. It does not repro with:

  • Client-side Blazor
  • Server-side Blazor with no prerendering
  • Server-side Blazor with static prerendering

Since stateful prerendering is being decommissioned, this issue can just be closed.

@SteveSandersonMS SteveSandersonMS added ✔️ Resolution: Won't Fix Resolved because we decided not to change the behavior reported in this issue. invalid and removed ✔️ Resolution: Won't Fix Resolved because we decided not to change the behavior reported in this issue. labels Jul 21, 2019
@ghost ghost locked as resolved and limited conversation to collaborators Dec 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-blazor Includes: Blazor, Razor Components bug This issue describes a behavior which is not expected - a bug.
Projects
None yet
Development

No branches or pull requests

2 participants