[WASM] BreadcrumbBar isn't responsive

[morning4coffe-dev]

Current behavior

Recording.2023-06-01.004318.mp4

Expected behavior

No response

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

http://playground.platform.uno/#aa5e4903

2. Resize the window

or

1. Go to Gallery
2. Look for BreadcrumbBar
3. Change the window size

Workaround

No response

Works on UWP/WinUI

Yes

Environment

Uno.UI / Uno.UI.WebAssembly / Uno.UI.Skia

Uno.WinUI / Uno.WinUI.WebAssembly / Uno.WinUI.Skia

NuGet package version(s)

No response

Affected platforms

WebAssembly

IDE

No response

IDE version

No response

Relevant plugins

No response

Anything else we need to know?

No response

[jeromelaban]

If this does not happen with WinUI, we may not be having the latest sources?

[morning4coffe-dev]

@jeromelaban i have tested it on WinUI project also and I am getting the same issue. I have updated this with playground link.

[jeromelaban]

@morning4coffe-dev when you're saying you tested on WinUI, you mean a WinAppSDK project?

[morning4coffe-dev]

@jeromelaban yes 👍

[jeromelaban]

I see, so the section in the original issue saying works on UWP: Yes was incorrect. This would mean that it's not an issue, but rather a behavior from the official implementation of the control. /cc @MartinZikmund

[MartinZikmund]

@jeromelaban that was a misunderstanding, it does work correctly on WinUI, it does not on Uno, so the issue is valid

[Arieldelossantos]

hey @MartinZikmund / @kazo0 i've been working with this issue and i noticed that the issue is reproducible on the Wasm Sample app on Uno.UI when screen is resized to smaller width than the breadCrumBar content... so the method that is hit is MeasureOverride...

the issue is that the first node (Root >) keeps visible

the weird part is that if we add another node, the first node hides and the behavior works as espected

any idea on which other method i should be looking on when resizing screen???

[MartinZikmund]

It should definitely happen somewhere withing the Measure/Arrange phase, but it is quite possible that the root cause will be hidden somewhere within the ItemsRepeater code, which is quite complex...

[Arieldelossantos]

as you mentioned @MartinZikmund the issue apparently is coming from the itemRepeater and the Arrange method from the UIElement class :/