Hey what now? Something new with the component library in this change? Or just the same old one?
I noticed a blank page/reusable element with no element will not load or allow you to see/change the element detail/inspector popup, please debug.
I recommend sending in a bug report, so the Bubble Team can patch all of them before releasing it to everyone; that’s what I’ve been doing as I see new bugs pop up
Having a weird issue with images:
- Image would not show in editor despite showing it in the element tree. It was set to collapse when hidden. Once turned off, it showed.
- Tried creating a group with the image and set that to Align to Parent. For some reason it’s parent element that was a Column layout all got scrunched up too.
Already did, no worry!
Hi, I enabled this feature, but didn’t see any improvement in performance… I don’t know if it’s just me. I created a theme where I was recommended to use this feature.
I also noticed one problem (it’s not in the standard working version) - If the input field is initially hidden when the page loads, there’s no way to show it in the editor either. Even I click on element in Tree. Only in the element tree (hidden) you can find it. Is this a bug or something new?
In standard version I can see hidden input field on editor area
I’ve just encountered this: group elements in… borks the visual placement of items.
@alcompstudio, yeah certain hideable things do not make themselves visible when visibility is toggled in the Elements Tree. This might be happening for all inputs as the one I observed was that a picture uploader (which is an input) that is set to be hidden on load will never show itself in the design/responsive view (it’s inside a repeating group). At least clicking in the elements tree brings up its property inspector dialog!
Yes, I can find hidden input in the item tree, but it’s not really convenient right now. I also want to see the hidden input as a visual element as well, to estimate its position on the canvas. In a working version of the editor, all hidden elements (including inputs) are displayed by clicking on them in the element tree.
But, there is another case: in the experimental version, other hidden elements are still displayed when you click on them (as before in the working version). And input fields are not displayed. Why does this happen? That’s what I asked - could it be a bug? After all, the other elements work!
YES, it’s a bug in the experimental builder. I was just CONFIRMING that someone else (ME) has also noted the same. We are talking about the experimental builder in this thread and discussing issues.
Oh, I’m sorry, I didn’t know what you were talking about right away! Thanks for the clarification!
+1 for proper use of “bork” @rico.trevisan! (I’m actually really impressed that there’s so little that’s wildly messed up in this new editor. Such a complex thing!)
Does that group have row gap set by chance? We are deploying a fix for grouping elements not working with row gap
This is a bug that is being fixed!
Is your page in a column layout by chance? Elements inside a responsive container type cannot be resized by clicking and dragging as their widths are controlled by the different responsive settings available in the Layout tab of that element
Yes, it did.
How can we know when new fixes are deployed?
It doesn’t look like these fields are updating.
We really need a change log for experimental features… I’ll update this thread
[BUG FIX] There was an issue with groups that had row gaps that caused some wonky behavior. Bugs involving grouping elements into a group or copy and pasting into a group should be resolved.
Please let me know if you are still seeing grouping related issues
Hey @nickc, have all of these bug fixes been pushed live to the experimental feature? I had submitted a few bug reports and the Tier 2 support team told me that it was a “Planned Fix”
Thanks! Updating us here is highly appreciated!