search

unoplatform / uno

Build Mobile, Desktop and WebAssembly apps with C# and XAML. Today. Open source and professionally supported.
https://platform.uno
Apache License 2.0
8.77k stars 706 forks source link

Verify Uno's behavior vs WinUI's behavior when both coercion and animations values are set #15529

Open Youssef1313 opened 7 months ago

Youssef1313 commented 7 months ago

Current behavior

In Uno, precedence takes over normally, meaning coersion value will be used

Expected behavior

Juding only from WinUI's code, they have this:

image

So, they first check IsAnimated and then return the animated value (assuming it's no overridden by a local one)

This means that if a Coercion value is available, it won't be used.

NOTE: The info here shouldn't be taken for granted (in case some magic happens in WinUI code somewhere). We should try to validate WinUI's behavior vs Uno's behavior using a runtime test before making a change.

How to reproduce it (as minimally and precisely as possible)

No response

Workaround

No response

Works on UWP/WinUI

None

Environment

No response

NuGet package version(s)

No response

Affected platforms

No response

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

Youssef1313 commented 7 months ago

Actually, I think WinUI doesn't have a Coersion precedence at all.