VisualElement.OnMeasure currently routes to some inconsistent logic compared to OnMeasureOverride

[PureWeen]

Description

VE.OnMeasure follows this path

Which calls this

It should probably call this in both places of the OnMeasure override

The checks on the constraints of "0" also is going to cause inconsistent behavior. MAUI treats zero as zero.

We should review all the measure code inside VisualElement and just force everything to route to the MAUI paths.

Right now we hit a lot of inconsistent behavior because

button.Measure
and
(button as IView).Measure

Do different things.

we should make it so those both do the same thing and then if users need to switch back to old behavior they can via a switch.

[mattleibow]

This is the new logic in OnMeasure after my PR #23725:

[mattleibow]

Why do we have both, and why does the old Measure -> OnMeasure do a whole bunch of min/max checks where the new one just returns the size?

They seem to be very different. IView.Measure -> MeasureOveride is just the desired size, but the old one is trying to do more. Do we even use the old path?

[bradencohen]

Can this also be fixed for Arrange?: #17417