Elements in same layout doesn't response IsVisible changes [iOS][Mac]

[enisn]

Description

When an element's IsVisible property is changed, other elements' position doesn't change, they stay in the same position.

Let me explain with following gifs. When I try the same scenario in Windows or Android, everything works great. But it doesn't work as expected on iOS and MacOS.

✅ Works fine:

Windows	Android

❌ Doesn't work as expected:

iOS	MacOS

Steps to Reproduce

1. Create a new project.
2. Add 2 elements in the same stacklayout and set a name for the first one.
3. Add a button to the page and set the first element's IsVisible as false.
4. You'll see, the second element won't go up and stay at the same position.

You can try the opposite, initialize the first element with IsVisible as false and set IsVisible as true via button. You'll see the second element will be rendered on the first element.

---

Also, I have a repository for my complex situation, you can clone and run SandboxTreeView project to reproduce the issue.

https://github.com/enisn/TreeView.Maui

Version with bug

6.0 (current)

Last version that worked well

Unknown/Other

Affected platforms

iOS, macOS

Affected platform versions

iOS 15.4

Did you find any workaround?

Unfortunetely.

Relevant log output

No response

[kristinx0211]

verified repro on ios15.4 with the above project.

[enisn]

The same problem can be shown there too: #3410 (comment)
Android elements go up when IsVisible is set false, but ios elements stay

[AidarNurmukhametov]

Hello, we are developing DevExpress .NET MAUI controls and experienced the same issue. It has a High priority for us and we do not have a workaround. Thank you for your help

[AntonKosenkoDX]

@kristinx0211 Hello! Any update on this issue?

[enisn]

@AidarNurmukhametov did you find a workaround?

[AidarNurmukhametov]

@AidarNurmukhametov did you find a workaround?

@enisn No, I don't. Temporary solution was to use another layout, I don't consider that a workaround, result is not the same

[hartez]

@AidarNurmukhametov Have you tried updating VS to the latest preview? This may have been fixed in service release 2.

[ghost]

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

[enisn]

I've tested it on version 6.0.486 and couldn't reproduce it. I think this is solved.