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