User State anomaly

I have experienced an anomaly with the user state conditional visibility feature.
I might have narrowed it down but has anyone else experienced a problem where it does not appear to be set correctly?
I placed two text boxes, one that displays when user is logged in and the other when logged out.
I placed a log in/out button on the same form.
It all worked, the text changed depending on the log in status.

I then added a div block around each text box so I could style the layout.
Then the conditional visibility stopped working even thought the log on/out button changed its label.

So I deleted the conditional visibility settings and re-created them. It works again.

Can anyone explain why adding the div blocks would break the user state?

Thanks.

It shouldn’t, but user accounts was finished somewhat abruptly and in the middle of working on that feature to resolve some component-related issues and access-group-specific element visibility.

My guess is that wrapping it in the div momentarily deletes and then recreates your element, and the user-accounts visibility settings may lose its bearing on the element, effectively breaking the connection.

That’s just a guess. Webflow has redirected energy at core features and some important future directions like Localization and Optimize, but we’re hoping that at some point ECom, User Accounts and Logic will all get another round of attention to fix some of the more severe limitations.

All of the subsystems have solid potential.

1 Like