Property editor (beta) update #2

[mike.alvarez]

Hi everyone,

Since our December 22nd update, the team has been focused on enhancing the new property editor and addressing issues that were slowing users down and causing confusion.

Thank you again for the thoughtful feedback you’ve shared. Below is a summary of the improvements we’ve made over the past two weeks.

What we’ve shipped since our last update

Dynamic data and expressions

• We fixed an issue where the “email” field would sometimes show as an option in expressions and dropdowns for data types that did not have that field.

• We fixed erroneous error states shown in the property editor.

• We corrected the list of fields shown when using the “Group by” operator

Workflows and data actions

• We fixed an issue where you could not select Page elements in “Set state” actions.

• We added back the ability to create new data types and fields from dropdowns listing data types and fields.

Conditional and layout correctness

• We fixed an issue where some properties could not be set in an element’s conditionals as previously expected

• We fixed an issue where incorrect properties were showing when conditionally setting an element’s height/width

• We resolved issues where certain properties (such as ID attributes) could not be removed once added to conditionals.

• We ensured the gap property for Repeating Groups was not erroneously showing.

• We addressed cases where the page builder dimensions allowed invalid decimal values.

• We fixed an issue where the property editor in the Styles tab for Pages would get cut off screen.

• We fixed an issue where in Style conditions, color pickers would be stuck expecting dynamic expressions rather than allowing static values.

Expression and editor behavior

• We fixed an issue where dropdowns would sometimes get cut off towards the right hand side of the screen

• We removed the overlay that prevented opening up expressions from the property editor in the Live branch

UI polish and consistency

• We fixed several visual inconsistencies, including misaligned controls, and changelog previews being cut off.

• We Improved labeling and captions to reduce ambiguity, including standardizing text casing.

• We fixed cases where gray warning components appeared even when there was no message to display.

• We ensured plugin-related fields stretch out to show their full content

• We fixed an issue where the Appearance property editor tab was not showing for Column elements

• We ensured the style for the Line/Bar Chart element displayed correctly with the new Property Editor.

Beta access and rollout hardening

• We added changelog entries to better document recent style and transition changes

• We fixed an issue where the param field in the “Run javascript” action could not take dynamic values

What we’re actively working on

Editor clarity and scan-ability

• We are Improving how empty values, dynamic expressions, and static values are visually differentiated, especially in parameters/properties.

• We are giving dynamic expression previews more space so complex expressions are easier to read at a glance.

• We are increasing contrast and improving section headers, tooltips, and overall readability across the editor.

Expressions, conditions, and correctness

• We are addressing remaining issues with conditional styling, including border styling resets, background color conditions, and column gap inconsistencies.

• We are fixing popovers that close unexpectedly during common workflow actions like “Do a search for”.

Workflow navigation and productivity

• We are making it easier to move between Design and Workflow while maintaining context.

• We are Improving the display of “Only when” fields in the Workflow tab property editor so there is more visibility

• We are ensuring undo correctly adds all fields in a data related actions.

UI behavior and interaction polish

• We are ensuring only one popover type can be open at a time to reduce overlap, confusion, and the extra clicks needed to close popovers manually.

• We are fixing popover stacking, z-index, and focus issues across the editor.

• We are delaying showing tooltips on caption hover and ensuring they do not remain visible when they should disappear

What we’re evaluating

• Improving UX of expression editing and validation

• Popover UX (Auditing the UX to determine if there are ways to reduce the amount of nested popovers)

• Workflow name overflows behavior

• Do a search for - popover styling and UX

Thank you again for your detailed feedback. It’s helping guide our improvements and ensuring we build the best possible experience. We remain committed to continuing to review your feedback and making the property editor even better throughout this beta.

We’ll share another update the week of January 19th. Thanks, as always, for your continued partnership!

Mike

[Sergiofojr]

Cheers, Mike. Thanks for sharing
I can’t wait to test too haha I want to be a beta test on that

[boston85719]

@mike.alvarez

Editor clarity and scan-ability

• We are Improving how empty values, dynamic expressions, and static values are visually differentiated, especially in parameters/properties.
• We are giving dynamic expression previews more space so complex expressions are easier to read at a glance.
• We are increasing contrast and improving section headers, tooltips, and overall readability across the editor.

After these I’ll likely start testing it again. Looking forward to these.

[randomanon]

Awesome, glad to see you guys are rapidly iterating and improving things based on feedback.

Any chance we will get nested expressions?

[rico.trevisan]

Wow, that’s a ton! Thanks for the continuing development and communication.

[asked111]

Thank you

[bonjour_17]

Seriously disapointed of non being involved in the beta

[finitejest]

I really appreciate this level of update / detail!

[NexradJosh]

It’s great to see these updates! I’ll give it another try this week and see how it feels.

[rafaelchavantes]

Thanks for the update!

I will start testing again!

[fede.bubble]

@bonjour_17

Seriously disapointed of non being involved in the beta

No worries here, as the beta moves through updates it will become accessible to more and more users. You’ll still have plenty of time to test before it goes into GA for everyone

[J805]

I keep getting weird stuff like this happening @mike.alvarez

[J805]

Another bug here, you can see the old editor works just fine but with the new editor we can’t do the same thing. It shows red. It doesn’t have an error, so it might still work, but the old editor works fine. @mike.alvarez

I am assuming this is where is should report bugs since the Support staff at Bubble is very difficult to work with. Have to go through a bunch of people that don’t know what they are talking about until we can finally talk to someone that knows what is going on.

If this is an error, this should be red like it used to be in the old editor:

This is showing an error in red when there isn’t actually any errors in the workflow anymore.

Is this supposed to show up on the left side now? Really weird. Since the button is on the right, I would expect the menu to show up underneath it. Not on the left side of the screen.