Mike Crider

It looks like your theory is correct that this issue is specific to Win10.

WinUI currently doesn't support the environment parameters. This capability is on the backlog for the future.

@myblindy The raw version tag indicates the version the bug was introduced in (if known), and in this case the bug was introduced in 1.1. The issue will be fixed...

Closing as fixed in 1.1.4.

I agree using the FallbackColor downlevel is the right design. [Internal tracking issue](https://dev.azure.com/microsoft/OS/_workitems/edit/40223875). @JPTGamesAndApps The issue you mention sounds like what happens if `Close()` isn't called on the old controller...

I'm currently not able to repro the crash, perhaps because I'm trying the repro on Win11 rather than Win10. From what I can see of the callstack, I don't see...

Yes, I needed to offset to the drop zone (which I see is logged as #7008) and I see the Move label along with the "OnDragOver" text in the debug...

Related to microsoft/WindowsAppSDK#2412. That regression was fixed in 1.1-stable, but this issue shows that the new Mica and Desktop Acrylic features unfortunately have a similar issue which needs a different...

@huoyaoyuan The fix will be in WinAppSDK 1.5. It did **not** make it into the 1.5-experimental2 release today.

The PowerManager code appears to be broken. From the code, I wouldn't expect the event to ever fire or for getting the property value to ever work. Logged ([internal bug](http://task.ms/47688795))...