Eilon Lipton

Hi @raymondjstone can you also show screenshots of what you're seeing and point out what it is that you expect?

@jknaudt21 very nice! Can you confirm what happens with: 1. `dotnet new maui` 2. `dotnet new maui -o FooBar_Baz.Banana` I want to make sure that those cases are also handled...

Apparently there are no further Ventura-related issues, so as long as everything is up-to-date, it should be fine. Check updates for Xcode, Visual Studio, and .NET.

Some folks looked into this and apparently it's an issue due to arm64/x64 differences in various binaries used in such projects. You can read more here, including a workaround that...

I confirmed that this repros as-is with Blazor Hybrid WPF.

And it seems to happen in Blazor Hybrid WinForms too....

But it does not repro in a WebView WinForms app. So perhaps some setting that Blazor Hybrid sets is affecting this...

Oh boy, it appears that setting `CoreWebView2.Settings.AreDefaultContextMenusEnabled = false` is what causes this: https://github.com/dotnet/maui/blob/main/src/BlazorWebView/src/SharedSource/WebView2WebViewManager.cs#LL379C4-L379C73 My vague historical recollection is that that setting affects only the "web browser" type of menus...

I figured out how to make it work but I'd say it's not a great solution. Ideally there would be an option `WebView2.CoreWebView2.Settings.AreWebSpecificContextMenuOptionsEnabled = false` to disable only the "web"...

For more _context_ on how to handle the `WebView.CoreWebView2.ContextMenuRequested` event, check out: 1. This spec: https://github.com/MicrosoftEdge/WebView2Feedback/blob/main/specs/ContextMenuRequested.md 2. The docs: https://learn.microsoft.com/dotnet/api/microsoft.web.webview2.core.corewebview2.contextmenurequested?view=webview2-dotnet-1.0.1418.22