Curious if something changed on the backend… this absolutely used to work.
I have a footer that’s really a floating group with two reusable elements inside (one is the full expanded footer, and the other is a “collapsed” version).
The collapsed footer is visible on page load, the other is not visible. The expectation is that when I hover over the group they’re in, the collapsed footer disappears, and the full footer appears.
Now, however, this doesn’t work at all. Instead, both footers appear, stack on top one another.
Anytime you have an element that is to be visible conditionally, always set it so that by default it is not visible on page load (in layout) and use ONLY ONE condition to make it visible. Then if you have two floating groups that need to be visible at different times based on the container group being hovered, you would have the following setup:
Floating group A: not visible on page load, conditionally visible when ‘group is not hovered’
Floating group B: not visible on page load, conditionally visible when ‘group is hovered’
You could try hiding the collapsed footer from a workflow.
1.Use the Trigger “when condition is true” and set it it run Only When Footer A is visible.
2.Hide the element Footer Collapsed A
Like @boston85719 said, also uncheck “visible on page load” for both items and add a condition to render the RE on page load. Such as when “Footer A is not visible” → “This element is visible”
