I’m currently running iOS 26 Developer Beta, and recently noticed a significant change in floating group behavior in Safari (specific to iOS 26). The change seems to be caused by Safari’s new UI, where the address bar no longer covers content in the bottom layer.
The result of the new behavior is that floating groups are pushed down from the top and up from the bottom, making it impossible to use floating groups to create a full screen experience and cover the content behind it. On mobile, we’re using floating groups for two purposes: A full screen login page above content that should only be displayed to signed in users, and a bottom menu bar. As you can see in these screenshots, the resulting UI is absolutely disgusting.
We’ve tried to accommodate the new behavior as well as we can for now, mostly by removing the use of floating groups on mobile, but it’s a growing issue. Noticed other behavioral changes, most prominently that Search Box list results are now appearing above the input so you can’t see what you’re typing. Surprised there’s so little to zero attention on these issues, but if there’s one thing I’ve realized about this community using Bubble for the past 5-6 years, it’s that most Bubble-developers don’t care enough about design, particularly UX.
While @mossoc99 was kind enough to provide a temporary workaround, I didn’t hear back from you @fede.bubble . Is your team aware of the issue and working on a permanent fix?
I am also struggling with this…has anyone figured out a workaround?
edit - the html snippet is helping. still, I’m surprised that there aren’t tons of Bubblers freaking out over this. all my pages have a floating group header and footer - it ends up being crucial for the mobile experience
Sadly a sign that the average Bubble-developer (just was with developers in general) isn’t obsessed with UX… But yes, the snippet fixed the issue for me, and thank God for that since Bubble seems to not give a s*** despite the bug reports.
It looks like this snippet breaks the “scroll to an element” and “scroll to an entry in RepeatingGroup” actions. unfortunately matters a lot in my app. Anyone know what to do here?