Peter Morris

Passing state down through [Parameter] in Blazor causes a re-render of the receiving component whenever the parent component renders. If they get their own state, it means they only render...

Yes, but make sure you call InvokeAsync, just to be safe. You could also use StateSubscriber, which automatically subscribes + unsubscribes + notifies. Either way, make sure you implement IDisposable...

Here is the official documentation... https://docs.microsoft.com/en-us/dotnet/standard/garbage-collection/implementing-disposeasync It seems to me that adding IAsyncDisposable to a base class would require all descendant classes to also implement the pattern. Looks to me...

I think this means it'll have to be a breaking change and implement IAsyncDisposable instead of IDisposable. I'll have to give it some thought, but it would be a V6...

Hiya Please submit a PR based off release/5.5 and we can discuss the implementation :)

Your effect should consume the stream and periodically dispatch actions to update the state.

As DOM elwlents are owned by components, elm.GetOwningComponent()

Selenium will be slow. Could you use the Blazor HTML render to create your HTML string, set the HTML in a browser component, and have some kind of interceptor for...

Selenium is what the Blazor team uses, but I expect they aren't happy that a single test takes a few seconds - which is one of the reasons bUnit is...

> A browser component Something that will work on Windows, Mac, Linux: Like the Steve Sanderson used here - https://github.com/SteveSandersonMS/WebWindow > the problem is when JavaScript needs to execute to...