MikeHillberg

The Xaml markup parser does this as a convenience helper; automatically converting the Color into a SolidColorBrush. So in this case ControlStrongStrokeColorDefault is a Color, consequently RadioButtonOuterEllipseStrokePointerOver is a Color,...

@michael-hawker, what list interfaces does your collection implement?

And it looks like IList but not IList<T>. IEnumerable or IEnumerable<T> should be enough.

I'm sorry, the [PrintDocument](https://docs.microsoft.com/uwp/api/Windows.UI.Xaml.Printing.PrintDocument) API hasn't been updated for WinUI3 yet, and it's an accident that the API is showing up right now. I'll look into the roadmap, but it's...

This crashes for you just running from VS (Control+F5)? I put your markup in a new app, set `true` in the project file, and can't repro the crash.

Thank you @ghost1372! @DrusTheAxe? 00 Microsoft_WindowsAppRuntime_Bootstrap!MddBootstrap_StopActivity 01 Microsoft_WindowsAppRuntime_Bootstrap!wilResultLoggingThreadCallback 02 Microsoft_WindowsAppRuntime_Bootstrap!wil::details::ThreadFailureCallbackFn::NotifyFailure 03 Microsoft_WindowsAppRuntime_Bootstrap!wil::details::ThreadFailureCallbackHolder::GetContextAndNotifyFailure 04 Microsoft_WindowsAppRuntime_Bootstrap!wil::details::GetContextAndNotifyFailure 05 Microsoft_WindowsAppRuntime_Bootstrap!wil::details::LogFailure 06 Microsoft_WindowsAppRuntime_Bootstrap!wil::details::ReportFailure_NoReturn 07 Microsoft_WindowsAppRuntime_Bootstrap!wil::details::ReportFailure_Base 08 Microsoft_WindowsAppRuntime_Bootstrap!wil::details::ReportFailure_Msg 09 Microsoft_WindowsAppRuntime_Bootstrap!wil::details::ReportFailure_HrMsg 0a Microsoft_WindowsAppRuntime_Bootstrap!wil::details::in1diag3::_Throw_HrMsg 0b Microsoft_WindowsAppRuntime_Bootstrap!wil::details::in1diag3::Throw_HrIfMsg 0c Microsoft_WindowsAppRuntime_Bootstrap!FindDDLMViaEnumeration...

We've done some work to correct these events, but ran into some compatibility issues and not shipped any fix yet. The Loaded event is raised during a layout/render tick. So...

It's getting into an infinite loop where layout A is triggering a response to change layout to B, and that's triggering a response to change layout to A, B, A,...

Adding @ranjeshj.

Thanks for the repro. We've done some debugging and the issue is that the button on the page that's being navigating away from has captured the pointer (normal for pointer...