Andrew Nosenko

That'd be a great feature :) I know Luke Sampson has [his own version of sudo](http://blog.lukesampson.com/sudo-for-windows), although I found out about it only after I had created mine. Haven't looked...

Thanks for the feedback, it's a good one, I hope to get to it when I have some spare time.

@lukekarrys Node v22.1.0 was out, and I had to patch `"C:\Program Files\nodejs\npm.ps1"` again. My current version: ```PowerShell #!/usr/bin/env pwsh $NODE_EXE="$PSScriptRoot/node.exe" if (-not (Test-Path $NODE_EXE)) { $NODE_EXE="$PSScriptRoot/node" } if (-not (Test-Path...

> Andrew's [solution](https://github.com/npm/cli/pull/7458#issuecomment-2093920138) is working well. @mbtools , thanks for vouching! I currently re-apply this patch semi-automatically everytime I upgrade node.js on Windows: https://github.com/npm/cli/issues/7375#issuecomment-2437224225 I'm sorry I don't have capacity...

@joperezr, thanks for your thoughts. I've just tried it with the .NET SDK 5.0.100-preview.7 and it **still bundles** the WPF assemblies. That was very easy to do under Windows Sandbox,...

This keyboard issue is hindered by the fact that the WebView2 host's child window (created by `HwndHost`) and the actual hosted Chromium HTML renderer child window are residing in separate...

TBH, at this stage I feel like the best path for hosting `WebView2` is to implement a custom wrapper on top of [`CoreWebView2`](https://docs.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.core.corewebview2?view=webview2-dotnet-1.0.902.49) and [`CoreWebView2Controller`](https://docs.microsoft.com/en-us/dotnet/api/microsoft.web.webview2.core.corewebview2controller?view=webview2-dotnet-1.0.902.49). That would give me direct...

Hi @champnic, thanks for putting it on track. FWIW, the current keyboard/focus behavior is a lot better than that of `BlazorWebView`, at least in its current iteration where it's practically...

@zhuhaichao518 thank you - well done, good to see some progress! I'll give this new feature a try and will report what I'll find.

This is a real issue, e.g., Microsoft's own `#azure-devops` and `#playwright` add more than 128 tools.