I have a reusable element on a page, my header. The reusable element has a floating group set to float above all elements. That floating group is the header menu.
On the page I have a floating group set to float above all elements. It displays a selected product.
On the page we have features of send to back and bring to front that are the ONLY ways Bubble allows us to set a z-index of elements. When I use the send to back for the floating group on the page and the bring to front of the reusable element you can see in the element tree the switch take place…however, when the floating group on the page is visible and I show the floating group from the reusable header, the floating group of the header is underneath the floating group of the page.
This doesn’t make sense as the reusable element is set to bring to front while the floating group on the page is set to send to back.
Is this a Bug or do I just have my expectations set logically when I should just throw logic away?
Yes. On the reusable element itself I used the bring to front on the fg. On the page where I placed the reusable I used the bring to front on the reusable and for the fg on the page I used the send to back. Even doing that, the fg of the reusable is still beneath the fg on the page.
Interesting. Do you recall the order in which they were added to the page? I wonder if deleting the reusable and re-adding it would result in it being assigned a higher z-index. Just a thought…
I saw this recently when i had a group focus in a repeating group (inside a reusable element) show up above a popup. Really weird, so i just hid the group focus when they clicked on the button. I do think it might be a bug though. If you can reproduce it and have the time to do the bug report, that would probably be best. I would do it, but I just don’t have time to deal with the bug report process.
Thanks for the suggestion. I was wondering if it might be similar to the popup creation order issue as well. Definitely could have been. If I can remember tomorrow, I’ll still test it out.
I have reproduced it and I did submit a bug report September 23rd. As I am writing this to check on that date, support replied today (they did reply earlier and we’ve had 18 emails on the email chain on the subject) with the following:
Thanks again for your patience. I actually learned that a floating group nested within a reusable element will not act as a floating group if the reusable element itself is not set as a floating group
I just put together a quick test page and it works. My header reusable element was originally set as a group, because on some pages I want it to float and on others I don’t. Now knowing how this functions I can move along.
I would do it, but I just don’t have time to deal with the bug report process.