If this is not the best place for this I apologize.

Toggling an elements visibility using the eye icon in the navigator doesn't always set the elements visibility. Also, if it does and there is a binding set for visibility it removes the binding. Not sure if this is intentional or not but seems like a bug.

Hey GausRoth, this is Dorian! Glad to see you made your way over here from YouTube :)

Don't worry, you've come to the perfect place for this, and we really appreciate you taking the time to reach out.

I've just spent some time running through your scenario regarding the Navigator Visibility Toggle and Visibility Bindings, was able to replicate it, and it absolutely appears to be a bug.

I've just created a Ticket for us to address this: #0004581 --- we'll get this fixed.

Outside of the Binding overwrite issue; in terms of the eye icon toggle in the Navigator not always reliably working -- do you by any chance have any reproduction steps and/or a file you could share with us in which this occurs at a high rate?

Thanks again, and please do let us know if anything else comes up!

- Dorian

I have also not been able to reproduce the visibility issue with the eye icon. My project has many children and I duplicated a big portion of it so it could have been a combination of that but I just tried to repo and was unable.

Hi GausRoth,

Thanks for the reply -- what you mentioned around duplication sounds probable, especially if compounded with the Bindings issue from before where it seems like in the XAML it was actually conserving the Binding despite it displaying differently in Studio. It's very possible this could have spread, and caused some discrepancies. Hopefully this remains something you don't encounter again, but if you do - please let us know.

- Dorian

It is happening again and from what it looks like is the eye icon is swapping between hidden and collapsed. In the data set I have it set to Collapsed so I wonder when I hit the eye icon and it removes the visible binding it sets the default to whatever I had the data set to. I changed it to Hidden in the data set and now when I press the eye icon it stays set to hidden. If I set the data set to Visible the eye icon works as expected. It still removes the binding though.

Also setting the visibility in the properties panel does not change it in the navigator. It seems that if a binding is created and the data set was not visible when it was removed via the eye icon it breaks it. Setting all of them to Visible makes the eye icon work. Clearing the local value fixes it.

Hi GausRoth,

Thanks for the additional reports, I'll touch on each one-by-one:

It is happening again and from what it looks like is the eye icon is swapping between hidden and collapsed. In the data set I have it set to Collapsed so I wonder when I hit the eye icon and it removes the visible binding it sets the default to whatever I had the data set to. I changed it to Hidden in the data set and now when I press the eye icon it stays set to hidden. If I set the data set to Visible the eye icon works as expected. It still removes the binding though.

I've been able to reproduce this on my end. This seems to be centred around the same issue as in #0004581 where there is some desync between what's displayed in Studio and what's written to the XAML.

Also setting the visibility in the properties panel does not change it in the navigator. [...]

This one is working as intended however. Basically the Navigator 'eye' icon and the Visibility Property are meant to be independent of one another, and provide slightly different functions.

The 'eye icon' can be considered a 'design-time' tool meant to only impact what is displayed whilst authoring documents in Studio.

This can be seen for example, if you 'close the eye' on an Element (hiding it on the Page), then pressing 'Play' (Ctrl+P), and seeing that the Element that was hidden in 'Edit Mode, is visible in 'Play Mode'.

The Visibility Property however, not only impacts the visibility of an Element in 'Edit Mode', but will also carry forward into 'Play Mode' (and into the Runtime too).

This is why when changing the Visibility Property in the Properties Panel, does not reflect in the 'eye icon'.

The bug here is that in the other direction, the eye icon in the Navigator shouldn't be impacting Visibility Property itself.

Thanks again!

- Dorian