-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[browser] Minimal legacy support for Blazor renderBatch #95869
[browser] Minimal legacy support for Blazor renderBatch #95869
Conversation
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsThis will allow us to reduce dependency of Blazor internal on legacy interop to last 2 methods. Contributes to dotnet/aspnetcore#48042
|
@pavelsavara Would it be correct to think that a test can be added only once the other linked PRs, that use the bits added here, get merged? |
I tested it locally together with local Blazor. This is core of Blazor rendering, so we would know pretty soon that I broke it. I hope they have tests for it. |
This will allow us to reduce dependency of Blazor internal on legacy interop to last 2 methods.
Contributes to dotnet/aspnetcore#48042
To be used by dotnet/aspnetcore#52732