ShaunLoganOracle

@champnic This issue is still occurring using WV2 SDK 1.0.1832.23 and RT 114.0.1823.67 Is there any progress/update?

> does the solution mentioned in #1254 work for you? @novac42 In a very quick test, this approach looks promising. I added `--enable-features=msWebView2BrowserHitTransparent` to the `CoreWebView2EnvironmentOptions.AdditionalBrowserArguments` used when creating the...

There is one non-intuitive behavior: clicking the mouse in the HTML content rendered in the WV2 control does not give keyboard focus to that control. The keyboard focus stays in...

@novac42 @zhuhaichao518 We have found a blocker issue for us with the `--enable-features=msWebView2BrowserHitTransparent` switch enabled: In a WinForms modal dialog that hosts a WV2 control which renders a login form,...

FWIW, I have the same/similar issue building my VSTO add-in for Excel in VS2022 (targeted to .NET Framework 4.8). After upgrading the WV2 SDK from 1.0.1774.30 to 1.0.2739.15, I get...

Please restore the previous functionality. Once we upgraded VS 22 from 17.8 to 17.11, our use case (VSTO Add-in for Excel, .NET Framework 4.8, FxCopCmd.exe) is completely broken for Code...

@arunchndr I upgraded to VS2022 17.12.5 and I still see both issues previously reported: 1. Suppressed build CA Warnings are appearing in the error list (screen shot below) 2. Right-click...

> Does the lightbulb on the item (in source code) have an option to suppress that issue (at the document, or solution level)? No. There is no lightbulb in the...

@dibarbet Yes, those are FxCopCmd.exe build errors. More background in the [post above](https://github.com/dotnet/roslyn/issues/74228#issuecomment-2627599500). Yes, if I change the filter from "Build+Intellisense" to "Build Only" I still see the CA1007 that...

Yes, the CA1007 warning appears both in the Error List window as the previous screen shots show, and also in the Output window with "Build" selected as seen here: