So far the new engine is great and much faster for me. Spent the last few days converting reusable objects, and it’s been mostly smooth so far, except for one issue with collapsing groups that wasn’t present in the legacy editor.
For some reason, it appears there is a delay before groups collapse. So, showing a popup, for instance, with multiple collapsable groups will show the space of groups hidden by default before properly collapsing. Unfortunately, I haven’t been able to find a workaround other than maybe using animations when groups collapse to ease the transition (which isn’t ideal).
Maybe it is very obvious but I can not figure out how to inject a group (container) in between existing groups. (containers)
I think pages become very complex to “fix” when they are converted to new responsive mode. It is container inside container inside container inside another container etc. (still have a great respect to the team who came up with the conversion algorithm)
@nick.carroll Building a new app and am ready to go all in on the new engine. Any way to trigger the new engine by default in each new page? Perhaps a toggle in the App’s Settings?
I was able to fix my group focuses! I’m not sure if they pushed and update or I just missed it the first time around, but whenever I converted my page to the new engine, it set all of my group focuses to a fixed width and height, and set those values to 0.
I changed them to something reasonable and they worked.
Well done Bubble team for this new responsive engine, there is a bit of a learning curve but I’m sure we will save a lot of time in the end vs. the previous version.
I am struggling with one particular page layout where I want to show
A/ A left floating menu and
B/ the content of the page on the right of this menu. The content is left aligned on desktop (i.e. for large screens).
Now on mobile, I’d like the left menu floating menu to be hidden and the content of the page to be center aligned. And I can’t seem to make this work.
Each of the coloured boxes is a separate row that is hidden by default and only shown when the tab is selected. However, the popup shows the full height initially and then collapses. You can check out the editor configuration and demo here.
I have been waiting forever for this update. So awesome that its finally here.
I think all my apps need to be rebuilt from scratch to accommodate, but I’m so glad it has arrived.
Yes, the css used to get the 100vh is not working in the new engine.
I have test pages with same elements in the editor the team could take a look at as an example…one page is with new responsive engine and the other is with old responsive engine.
Am i the only one setting the minimum hight and width always on Zero ( 0 ) and then always use “Fit to Content”. In the first tutorrials i saw a lot of people working with margins all the time…
It rememberes me on the “Autolayout” Hug Content function of Figma.
Also the padding inside a group is in bubble the margins of the object inside the group if i get this right.
Was there an answer to this? Drag drop is really helpful in moving elements around groups while keeping their workflow references intact.
“Copy with workflows” is not perfect, as it anyway creates a copy of the element and we need to change all the places where those elements are being referenced.
If disabling drag-drop, then we need a “Cut with workflows” and “Paste with workflows” too to maintain all the references of the element being moved around.
