Microsoft-ui-xaml: Unify Controls and Properties with Xamarin Forms

This was supposed to happen. Then XAML standard (announced a few years ago now) died and nobody from Microsoft has ever explained why. It's Xamarin Forms that needs to change to the other XAML flavors -- perhaps this would be better in their repo. I still can't fathom why they ever decided to change names like that.

@jrahma at this point in time, both Xaml and Xamarin.Forms have sizable developer communities and updating API names would constitute a significant breaking change. A renaming exercise just isn't feasible at this time for either framework. And adding new control aliases to Xaml (e.g. would just create a ) would lead to API bloat and runs the risk of making Xaml even more difficult to learn.

If you have suggestions for specific properties or features present in Xamarin.Forms but missing in Xaml, I would encourage you to open new proposals for the specific gaps.

We appreciate the feedback, however this doesn’t currently align to the project’s goals and roadmap and so will be automatically closed. Thank you for your contributions to WinUI!