[WASM] Problem with UserControl and ignoring settings

[HavenDV]

Current behavior

Differences(In WebAssembly relative to UWP): Width, Height, MinWidth, MinHeight, MaxWidth, MaxHeight are ignored

Expected behavior

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

https://github.com/HavenDV/Uno.WASM.TemplateBug https://github.com/HavenDV/Uno.WASM.TemplateBug/commit/b6a4c8ed81b38ced515ba79add7849c00d6191d4

Works on UWP/WinUI

Yes

Environment

Nuget Package:

• [x] Uno.UI / Uno.UI.WebAssembly / Uno.UI.Skia>

Nuget Package Version(s):

• 3.8.6 and 3.9.0-dev.104

Affected platform(s): Possible multiple, tested only on WebAssembly

• [ ] iOS
• [ ] Android
• [x] WebAssembly
• [ ] WebAssembly renderers for Xamarin.Forms
• [ ] macOS
• [ ] Skia
  • [ ] WPF
  • [ ] GTK (Linux)
  • [ ] Tizen
• [ ] Windows
• [ ] Build tasks
• [ ] Solution Templates

IDE:

• [ ] Visual Studio 2017 (version: )
• [x] Visual Studio 2019 (version: latest)
• [ ] Visual Studio for Mac (version: )
• [ ] Rider Windows (version: )
• [ ] Rider macOS (version: )
• [ ] Visual Studio Code (version: )

Relevant plugins:

• [ ] Resharper (version: )

[jeromelaban]

Repro archive: Uno.WASM.TemplateBug-master.zip

[jeromelaban]

@carldebilly Are we ignoring MaxWidth/MaxHeight and others when setting the Width/Height properties?

[HavenDV]

This looks like the most difficult and important bug of the series described, because the initial width and height are also ignored, so the parent control has MinWidth = "30" and MinHeight="30". The problem only exists if there is a separate UserControl, and the ContentControl and its derivatives are also used (usually in templates)

[carldebilly]

This could be related to https://github.com/unoplatform/uno/issues/2983 (it's not using shapes at all, so not related).

@jeromelaban we are reusing the same Min/Max/Value logic than Windows. But on Wasm, we're not using the layouter. We'll need to check on Skia...

[Youssef1313]

Maybe https://github.com/unoplatform/uno/pull/13391 can have an impact?