Open queequac opened 4 years ago
Thank you for the report.
Currently the layout engine still has corner cases like these ones that are not well supported, particularly when children request a larger size than what the parent offers. We're gradually improving the behavior by getting closer to the original UWP behavior.
/cc @carldebilly
https://github.com/unoplatform/uno/pull/13391 might help. Let's see Nope, this issue was for Android.
https://github.com/unoplatform/uno/pull/18261/ will probably fix this
Current behavior
Given a Frame control with a fixed size (Width="300" in the sample below), the size is not respected if the parent element provides less space (a Border with Width="100" in the sample below).
Instead the Frame shrinks to its parents size.
In the sample below, the Frame gets only a width of 100 and textwrapping occours after 100px. In case of an animation of the parent's width, the frame's content is re-layouted throughout the whole animation and the text wrapping dynamically depending on the parents size.
Note: If the Frame is smaller than the parent, the behavior is correct. Tested with Android 9 and 10
Expected behavior
Same behavior as under UWP. While the border restricts the size to 100, the Frame has still a width of 300 and content gets clipped. Frame's content remains static even if parent resizes.
How to reproduce it (as minimally and precisely as possible)
Configure a page like the following.
Environment
Nuget Package Version(s): Tested with 3.0.17 and 3.1.0-dev.741
Affected platform(s):