I have already submitted this as a bug report in the chat, but hoping we can get a little momentum here to help escalate this.
When set to wrap horizontally, all existing repeating groups set to wrap (no matter how they are styled) now show a grey dashed line as a separator. Even though they are set to have horizontal and vertical padding when wrapping. We cannot possibly catch all instances of this across ALL of our client projects. The only way we have been able to fix it on the ones we have caught is to set it back to fixed rows or columns, remove the styling, and then set back to wrapping.
Can you please help remove ANY separators if we are using the wrapping styling? Thank you!
Anyway, until a fix is deployed, the work-around is to temporarily switch the scroll direction to Horizontal in order to get the separator settings to appear, set it to “none”, and then change the scroll direction back to Wrapped horizontally.
That’s what I’ve noticed as well. It is just a bit frustrating to catch every instance of where we have used this type of formatting in RGs across all Bubble apps. Thanks for reporting as well!
I submitted a bug a week ago, and they haven’t helped me yet.
I noticed this was happening on repeating groups without a style attached, so if you create a style it’ll go away. But it’s annoying for me because I’m 3 months into a re-design so I can’t push a simple update.
Yeah, I’ve noticed this in some apps as well, basically what is happening is…
If you had a RG that had separators set (anything other than “none”), and now you have the “Display items as masonry grid” option checked, those separators will appear. To fix this, you’ll need to uncheck the “Display items as masonry grid” option and then set the separators to “none.”
Also, if you had a RG that had separators set (anything other than “none”), and now you have the “Set fixed number of rows” option unchecked, you’ll need to check this option again and then set the separators to “none.”
It seems that if you set these properties in the past but no longer use them, they continue to be persistently applied in the RG. I also believe this occurred after the implementation of the new “Reverse scroll direction” property.
The workaround I used to fix this was the same one already mentioned by @sudsy and @akamarski . Basically, make the separator option appear and set it to “none”.
Just a heads-up that this issue is a bit more insidious than initially thought. If you optimize your app and unwittingly expunge the Unused element property entries created by setting the Separators setting to “none”, Bubble automatically sets them back to the default (which is dashed separators), so you’re back to square one.
The root issue is that Bubble is honoring a setting that’s not even relevant for the configured RG scroll direction.
