Forum Academy Marketplace Showcase Pricing Features

New Responsive Engine [beta] is Live!

Similar to that, items that extend in groups just overflow on normal groups instead of allowing the group to scroll. Thanks!

Please keep us posted when these things are fixed and live so we can act accordingly, it’s hard to guess or follow the release notes.

Reusables that have been converted to the new responsive engine dont seem to accept data when placed in a popup in page that has not been converted. Havent tried to place them in a popup in a converted page yet. Anyone else have this issue?

Just curious if your group is set to Column layout mode. If so, I actually submitted a bug report on that 10 days ago. I just heard back from support today that this is “expected” behavior. I was rather surprised (to put it mildly) at that response. I honestly can’t think of a single scenario where a user would actually want that behavior as opposed to either scrolling or wrapping.

I just turned around and resubmitted it as a feature request. :confused:

Yeah, it was Column.

It’s an issue because if you want the group to scroll then you’ll need to use a Floating Group, but if you want to use the new horizontal responsiveness you can’t use a floating group because you can’t set the z-axis and they’re not in the same groups.

In the multi-line input there’s an option for “stretch to fit content” if that stretch to fit content isn’t checked then the content in the input scrolls. In the new responsive editor there is a “fit height to content” and that works great. But unchecked “fit height to content” seems like it should be have like that input and allow for a scroll in the group. I understand why there was a decision before the new engine since there was no option to fit height, but now, if I have a group in a group it should behave like a floating group (which has this option), but we can’t use because we can’t set z.

@sudsy - here’s a strange workaround: if you use a repeating group, instead of a regular group (the data type is User and the data source is Current User: converted to list… it creates a single item RG. This will allow the group to scroll around the RG and fill the space.

Odd, but it works?

1 Like

Hi David,

I’m not sure I fully understand the desired behavior based on your description. Is something like the following what you’re after?

In the above example, the sidebar disappears below page width 650px. (I just chose an arbitrary value.)

1 Like

Hi! Just asking again… is there any plan to include a “migrate as is” option to avoid the creation of new containers? Otherwise, Migration for large complex apps is not feasible and will leave many users that invested their resources fully into a bubble app behind with no real options. Full rebuilds are out of the question, and the current migration is a mess.

1 Like

Right, but what if you wanted the sidebar in this example to expand instead of disappear, and the content group should disappear? Only one of those two can expand/disappear. What if you wanted either to disappear? Of course, this can be done with duplicate elements, but you can’t use the same elements to do this.

Am I the only one who’s getting weird “line breaks” on styling today ?


1 Like

I thought at first it was an issue just to do with Font Awesome icons using BBCode but might be expanded BBCode in general - submit a bug report I reckon; Bug Report | Bubble

1 Like

will do, thanks

Hahah

I am unable to hide groups or elements with the new responsive engine. Only the contents within the group get hidden but not the group itself. It looks like you need to hide the parent group in order to hide the wanted group. Is that a bug or a wanted behaviour?

1 Like

Quick announcement everyone!

We just deployed the option when upgrading your existing page to the new responsive engine to upgrade “as is”. This means everything will be converted into fixed containers and your page will be structured essentially the same as it was before. Based on feedback, this should make converting more complex pages more straight forward. This does mean, however, that your page will not be responsive after the upgrade - you’ll still have to update your page and containers to responsive container layout types based on the responsive behavior desired.

The option to convert your page to the new responsive engine and match responsive behavior does still exist, but will lead to the extra groups required to map the old engine to the new engine.

We hope that this optionality will help you choose the best option for your use case. Look forward to hearing your feedback, thanks all!

10 Likes

Just deployed :slight_smile:

5 Likes

This is why I love this company and this team. You truly listen. I hope this helps many users adopt the new engine!!

2 Likes

@nickc I really love the new responsive engine, it’s so much easier to have control over how things behave and it’s much faster to build with this new engine. I’m in the process of building an app and I don’t want to use the old engine but there are too many bugs / plugins that don’t work / no selectpdf plugin etc. with the new responsive engine. What would you do in my case? Build on the legacy engine, or build on the new (beta) engine?

2 Likes

Is there going to be a forum section for the RE (responsive engine)? I ask because this page is getting quite long.

I have an issue when creating new groups at the end of a page/element tree, I can’t see the group in the editor (it does show up in the elements tree) but can see it in preview. Any suggestions on how to resolve this?
Thanks
Edit: Make Previous/First/Next did the trick to help find it (for some reason making it last after a centered repeating group its getting hidden somehow) but Im happy to find it for now and Im sure I’ll figure out why lol

3 Likes

PSA: in case you’ve encountered the bug where “Bring to front”/“Send to back” wouldn’t work with floating groups (as I have), here’s a quick note that Bubble has fixed the issue and ordering floating groups along the z-axis now works as it’s supposed to. :tada:

2 Likes

Same question here - To be or not yet to be RE (with so much of a bias to take the risk, hoping the fixed container would be a rescue boat)