Jérôme Laban

This issue is related to https://github.com/unoplatform/uno/issues/1940

We can repro with `2.0.512-dev.3874` The issues is related with the hit testing detection, where a type inheriting directly from `FrameworkElement` uses the default behavior of a transparent control cannot...

> @dr1rrb interesting, so there might be an issue with the underlying binding code there in Uno WASM (as it works fine in UWP and WinAppSDK). Will have to investigate...

Thanks for the report. Could you provide the full stack trace of the exception to help troubleshoot faster?

@lindexi once there's a working build for the SkiaSharp PR, we'll be able to validate if that helps.

@lindexi you'll need to either wait for an official skia build to be released in preview. You can upgrade all SkiaSharp packages in your uno project once those are available.

We may need to force an strong reference to some views and not rely on the CommandBar proxy's storage.

This caused by: ``` The expression """.Contains()" cannot be evaluated. Method 'System.String.Contains' not found. ``` Most likely because `_Pages` or others can be null. Either check for empty in the...

> In addition to this message, there is also such a message here, so I do not think that this is the reason > > ``` > src\SourceGenerators\Uno.UI.SourceGenerators\Content\Uno.UI.SourceGenerators.props(365,47): Error MSB4184:...

Currently, we're requesting the UWP SDK because the UWP-uno templates make use of it, but it's not the default path. We probably could remove this dependency in the walkthrough and...