Forum Academy Marketplace Showcase Pricing Features

New Responsive Engine Feature Request

As we all know the new responsive engine is in Beta…this means it is still missing some features that are planned, and that in turns means the community testing it can chime in with feature requests for Bubble to consider. Also, we all likely know that the ‘idea board’ could be improved and might not be the best way to request features for the new responsive engine specifically.

In my testing I have come across some things that I feel are missing and thought it would be a good opportunity to create a thread that others can add their feature requests to, or +1 or like other feature requests others add to this thread. This is in hopes that it would make things a little bit easier for Bubble to see what the community is requesting.

@nickc hopefully others will add their feature requests to this thread and it will make it more manageable to sort through all. So far it seems the announcement thread is filling up with a lot of questions, issues and feature requests, so figure something more dedicated would help out.

8 Likes

First request I would add here is to bring back to the text element the shrink elements height option, but could be used a bit differently than it had in the past.

To demonstrate the use case I made a video

I personally feel it would enable use to incorporate responsiveness, page breaks etc. in our Styles, specifically on Text elements.

7 Likes

Change the default size of elements from 400px to 280px, 300px or at most 320px

5 Likes

100% on this Matt

@nickc we need granular defaults addressing as this is impacting on build QC.

Thanks for firing this up, will keep a close eye on this thread

4 Likes

@nickc

2 more fundamental requests from a UI/UX perspective

  1. Padding controller

  1. Font awesome updated

10 Likes

I completely agree with you @boston85719
This option is also very useful to lower the number of element in a page because it works very close to the collapsing height for a group option!
For example i create all my buttons using a text and i show and hide them using the shrink elements height plus a condition instead of using a button into a group and then collapse the group height on a condition!

Hi

Playing a bit with new responsive system, I have one suggestion: It can be quite difficult to draw new elements, or move existing element to a group when you have ovelapping groups (let’s take for exemple the Tab layout template which I had to convert to the new responsive system).

It often goes to the wrong group. It is also a pain when you are converting pages from old system to new system and you want to simplify a bit the result by deleting/moving groups.

One usefull feature would be the possibility to assigne an element to a specific group by right-clicking in the element tree. What do you think?

4 Likes

I think there should be a keyboard shortcut to search for elements and then add to specific group.

2 Likes

I agree that a new way to move would be welcome - personally I’d love a drag-and-drop in the elements tree. My workaround, which works quite nicely now with this engine, has been to cut the thing you want to move, click the group where you want to paste it and then paste to locate it inside the group. Does that work in your scenario?

7 Likes

How about if the element tree has the option to ungroup an element or group?

Currently you hve to click on the group to do this, but if they are nested, it’s tricky.

3 Likes

YES!

I had submitted a bug to support regarding the fact that when you have nested elements (especially when the child element fills the entire parent element and therefore parent element is not accessible via the design canvas) and you hide them from the element tree and subsequently click into what you would expect to be the parent element on the design canvas, it is still selecting the child element.

The response from the engineer was helpful to understand why this actually expected behavior

Upon further investigation, I’ve found that this is expected behavior. In the new responsive engine, we purposefully do not remove hidden elements by default as that can effect positioning of other elements within the same container. In order to replicate the “Hide” functionality of old responsive, you can instead check “Collapse when hidden” on the element you are trying to hide. This will remove it from the canvas when hidden.

The instructions they provided do work, however, it does add extra confusion for anybody unaware of this, and adds extra steps that may not be necessary plus the fact that it could actually cause disruption to your design as the collapse height when hidden may not be desired and could easily be forgotten after making the change only to be able to select multiple elements and group them in a group.

In the original responsive engine I always made use of the multiple selection of groups with a right click to ‘group elements in a group’…

I believe a great feature to add would be to make it possible to select multiple elements from the element tree and right click to group in a group from there, instead of needing to do the whole process of checking the ‘collapse height when hidden’.

3 Likes

@boston85719 Thanks for that bug report.

My situation is that I have The Mother of all One Page Apps which I have converted to the new responsive beta. It has lots of groups now, many added automatically, some of which only hold one item and are candidates for removal after checking they have no sates and conditions…

I was working on the performance of the page and one thing I need to do is cull as many elements as possible to simploify things and make it lean.

I think I get what is being said about hiding rules being replaced by collapsing elements. Duly noted.

Yeah, your feature request is to allow us to select an element from the editor tree and ‘ungroup elements’…I’m basically saying yes because it is just the inverted concept I would like to see of selecting multiple elements from the element tree and ‘group elements in a group’.

I just think if they would be doing one, the other should be capable of being implemented as well.

1 Like

@boston85719 Ah. I see what you mean by inverted concept. This is true. I was looking at it much more simply … if it is on the right-click menu for a group, why not ‘just’ :wink: add the option to the right click of the element tree.

Another request … at risk of revealing a lack of understanding of the new Responsive Engine. ‘Horizontal stretch’ seems to be justified to the left and cannot be changed. I need images and groups to expand / contract within limits and to be centred. If I use ‘horizontal stretch’ the image or group is left hand justified if the parent gets bigger than the max. I’d like to be able to configure horizontal max to be left, right or centre justified.

I am missing the copy format. We had that in the old engine with the right click. I hope this is temporarily.
Screenshot 2021-11-11 at 19.02.17

This would be ideal.

Hi alxgrepe

Cut/Paset can do the trick sometimes, but when you have workflows and you don’t want to destroy them by cutting, anotherway of moving groups would be welcome :slight_smile:

2 Likes

‘Select parent / child’ is on the ‘Appearance’ tab.
I find I need it most in the ‘Layout’ tab.
If not moved, then a copy would be cool.

2 Likes