Mackinnon Buck

API Review notes: * We'll want to add a new `InternalServerError` method to `TypedResults` as well * Should we have another `InternalServerError` variant that includes an exception? * Conclusion: Yes,...

@halter73 Would you be able to look into this?

@rockfordlhotka I recall you mentioning that `LocationChanged` isn't sufficient to initiate the transfer of state from the client to the server, and that's because there's a race condition between the...

@rockfordlhotka > I continue to think it important that the events exist from Blazor page lifecycle or navigation such that we have some hope of implementing solutions. Thanks for the...

Closing this out. If we run into this problem again, we can open a new issue.

Hi @vflame, I tried you repro and I wasn't able to reproduce the bug: https://user-images.githubusercontent.com/10456961/210618275-02441293-8f97-4a54-bbfb-d8b8670febf7.mp4 Could you delete the bin and obj folders, clear browser cache, and run using `dotnet...

@vflame Thanks, that helps. Did clearing browser cache make a difference at all? I also see that there are some extensions active in Chrome - does disabling those make a...

Thanks for confirming the cause of the issue, @vflame. > As an enhancement, is it possible to return to Blazor what the offending DOM update/element was? It might be possible...

Thanks for reaching out, @pantoast. I believe the reasoning behind the current implementation was that any pending work relating to the change of the location should be canceled when the...

@pantoast One way is to have the parent component manage its own `CancellationTokenSource` that child components can utilize to cancel work that the parent is doing. Using `CascadingValue`, the parent...