Register default handler for blazor webview with TryAddHandler?

[miri10134]

Hello. After migrating to MAUI RC1 I found my custom BlazorWebViewHandler not working anymore, because the new AddMauiBlazorWebView-Method includes the following line:

services.ConfigureMauiHandlers(static handlers => handlers.AddHandler<IBlazorWebView, BlazorWebViewHandler>());

This requires custom implementations for IBlazorWebView-Handlers to be added after calling the method.
For example, the following code, which is just the default template with a custom handler configuration, will not work as intended:

var builder = MauiApp.CreateBuilder();
builder
	.UseMauiApp<App>()
	.ConfigureFonts(fonts =>
	{
		fonts.AddFont("OpenSans-Regular.ttf", "OpenSansRegular");
	})
	.ConfigureMauiHandlers(handlers => handlers.AddHandler<IBlazorWebView, MyBlazorWebViewHandler>());

builder.Services.AddMauiBlazorWebView();

return builder.Build();

Could the handler registration in BlazorWebViewServiceCollectionExtensions be changed to .TryAddHandler to prefer custom handlers, so developers don't need to be aware of the registration order?

services.ConfigureMauiHandlers(static handlers => handlers.TryAddHandler<IBlazorWebView, BlazorWebViewHandler>());

[richardhauer]

Thanks for logging this - I was trying to work out why my handlers were not getting connected.