Blazor WASM debugging appears to work with Chrome, but not with Brave Browser

[philipmorley]

WASM debugging appears to work perfectly well with some browsers, for example Chrome or Edge, but not with Brave. Please can you investigate why?

1. Install Brave, https://brave.com/?ref=dat003
2. Open Visual Studio 2022 > Create a new project > Blazor WebAssembly App > Next > Next > Create > Framework .NET 7.0 > Create
3. Go to BlazorApp1.Client/Pages/Counter.razor
4. Put a brakepoint in the IncrementCount method.
5. From the debug menu set the web browser to Google Chrome
6. F5
7. From the chrome browser window navigate to the Counter page, i.e. https://localhost:7224/counter
8. Click me
9. Observe that the Visual Studio debugger hits the brakepoint you setup from step 4.
10. Stop debugging.
11. From the debug menu set the web browser to Brave
12. F5
13. From the Brave browser window navigate to the Counter page, i.e. https://localhost:7224/counter
14. Click me
15. Observe that the Visual Studio debugger does not the brakepoint you setup from step 4.

[TanayParikh]

Hello, Brave isn't a supported browser unfortunately. Please see the following for the list of supported browsers: https://learn.microsoft.com/aspnet/core/blazor/supported-platforms?view=aspnetcore-7.0&preserve-view=true

[philipmorley]

Hmm. Thank you for your response. This makes me seriously re-consider our choice to use Blazor. We host a public facing website and we have no control over the browsers our customers use, and nor would we want to restrict them to certain ones. Does Microsoft plan to increase the number of supported browsers for Blazor? If not it would seem to me to be a fatal flaw with this technology.

[TanayParikh]

Given Brave is a Chromium based browser, core Blazor functionality should just work as-is. However this is not something we officially support. Your specific scenario of debugging not working in Brave is likely due to:

aspnetcore/src/Components/Web.JS/src/Platform/Mono/MonoDebugger.ts

Line 10 in a9b8828

? brands.some(b => b.brand === 'Google Chrome' || b.brand === 'Microsoft Edge' || b.brand === 'Chromium')

Note this is only for debugging purposes.

cc/ @danroth27 regarding the broader support feedback.

[danielgreen]

In Brave (checked v160.125) the brands array contains both "Brave" and "Chromium" so it should pass the test indicated above, which stems from #78907.

But breakpoints are still not hit in Counter.razor running in InteractiveWebAssembly mode in the Client project in VS 2022 17.8.3, when script debugging is enabled and the app is launched in Brave.
Breakpoints are hit when using Chrome and Edge.