Property Editor Beta Update #1

[mike.alvarez]

Property Editor Beta Update 12/22/25

Redesigned Property Editor

Hi everyone,

I wanted to share a product roadmap update on the property editor beta, including: what we shipped recently, what we plan to ship next, and broader improvements we’re actively considering.

Before I dive in, I want to thank you all for the incredibly thoughtful and detailed feedback you’ve shared. We’re reading every message, finding common patterns, and using the feedback to shape our next steps. We’re looking forward to your continued partnership as we make improvements, and wanted to reassure you all that we’re committed to closing the gap between where the experience is today and where it needs to be to offer a strong building experience for our users.

What we’ve shipped recently

Opt out toggle fix:

• Some users were unable to opt out of the redesigned property editor on Thursday, Dec 18. This was due to a minor error in how we segmented which users should get access to the beta. The opt-out toggle is now working properly for everyone, and we will introduce more testing before rolling the redesigned property editor to more users. Thank you to those who submitted this issue. This made it a lot easier for us to identify the root cause and ship a fix.

Editing and interaction

• Improved resizing for HTML and rich text editor popovers so content no longer feels constrained

• Added back keyboard accelerators for number inputs. Holding Shift + up or down now increases values by increments of 5

• Enabled users to set all margins/paddings or individual margins/paddings in conditionals for elements

• The property editor now remembers which conditionals are expanded or collapsed so context is preserved when navigating

• Fixed a bug where reordered properties would sometimes not be handled correctly in merges

• Fixed cases where users ended up in a mixed old and new property editor state, and had the version control sidepanel show on the left side of the editor even when the new property editor was not enabled

Dynamic data and expressions

• Improved positioning and behavior of the dynamic data button

• Restored the ability to reference reusable element properties in conditionals for reusable element instances

• Fixed multiple issues related to fields not being editable as expected

Workflows and data actions

• Made it possible to interact with the property editor in read-only branches to read expressions

• Added back an accelerator for “Add all fields” in data actions like Create a new thing

• Fixed missing parameters when setting width or height in conditionals

• Fixed cases where the page could not be selected in Set state actions

• Addressed several issues with options for workflow expressions not being correct

UI and plugin support

• Fixed cases where plugin “information” fields did not stretch dynamically

What we’re actively working on

Expressions and validation

• Making sure errors inside filtered expressions correctly surface at the top level (Today, nested expression errors aren’t visible at the top level, which forces you to click into expressions to discover issues. We’re fixing this so errors surface directly in the property editor, making it easier to spot problems at a glance)

• Fixing cases where valid expressions are incorrectly flagged as errors

• Ensuring expression dropdowns do not stretch beyond the width of the screen

Conditionals

• Restoring missing properties and THEN options in the conditional editor

• Fixing cases where certain conditional properties cannot be removed

• Correcting issues where column gaps and row gaps are mislabeled or misapplied

Layout and styling

• Removing the gap property from repeating groups

• Addressing cases where updating border styles resets other border settings.

• Resolving scenarios where page or element styles cause the property editor to get cut off

• Improving color picker behavior, especially in conditional styling (ensuring color picker does not expand outside the editor/canvas, ensuring the color picker does not stretch out when transitioning from list to grid view, ensuring color picker closes on click out properly)

Workflows and backend

• Cleaning up deleted fields still appearing in search filters and constraints

Readability and polish

• Improving overall contrast and visual clarity

• Fixing popovers that can get stuck under the menu bar

• Cleaning up tooltips and missing type indicators in expressions

Areas we’re actively evaluating

Based on the feedback we’re seeing consistently, there are a few areas we’re spending more time understanding and designing solutions for, rather than rushing out quick fixes:

• Reducing click count for several common user workflows (building dynamic expressions, building workflows from the design canvas, filling out fields of a workflow event/action, adding min/max height/width values)

• Making it easier to scan configurations and quickly tell whether a value is static, dynamic, empty, or invalid

• Improving expression readability and visual differentiation

• Re-evaluating the default width of the Property Editor and the sizing and spacing of controls like dropdowns and inputs to make them easier to scan and interact with.

The team would like to say a huge thank you again for helping us shape the best possible Bubble experience. We really appreciate all of the detailed feedback – it is directly informing our roadmap.

Our next update will be the week of January 5. We’re wishing you all happy holidays in the meantime!

Mike

[Sergiofojr]

How can I enable my Editor to access this new version?
My account hasn’t been enabled yet — is it possible to have it unlocked for testing purposes?

[randomanon]

Thank you @mike.alvarez, this is exactly what the community needs.

@mike.alvarez

Improving expression readability and visual differentiation

This is a must. The current method of showing everything in one giant run-on sentence CANNOT exist in a 2026 application. New users will instantly stop using Bubble, no matter how “nice” the design looks.

Currently the only way to parse expressions with parentheses is to:

1. Highlight each part one by one and do some weird mental math using Bubble’s internal highlighting logic which isn’t covered in the manual and can only be learned by understanding the patterns from experience, or
2. Ask an LLM and hope it gets it right.

Please see the below. They need to be nested appropriately and visually show the logic.

A good step in the right direction but ultimately pointless if you can’t implement the above.

[Newed]

Good job, @mike.alvarez. Posts like this allow the community to see what’s being done instead of figuring out by themselves what’s changed from last week to this week. It also gives us an overview of how things are being done and the direction they’re taking.

[carlovsk.edits]

Good job, @mike.alvarez!

When will the beta be available to other users? It hasn’t been released for me here yet.

[rico.trevisan]

Thank you for the update and engagement with the community.

[jo1]

great fixes and changes, god speed!

[mmahirf]

Nice work @mike.alvarez really enjoy these updates and understanding where things are heading. Looking forward to the next one!

[emir.ozgun]

Really like the speed, and it seems like you guys are actually listening.

@mike.alvarez

• Made it possible to interact with the property editor in read-only branches to read expressions

This got solved in 2 days. Pretty fast.

I have another niche feedback if you consider it, Currently I am using too much code, native elements don’t suffice, so I work with AI.

Lets say AI gave me a dynamic expression, around 200 words, containin current’users X, current user’s Y includes custome state Y’s number *…. and I cant copy and paste this to the expression editor due it doesn’t accept dynamic values when copy & paste, so if AI made some mistake or later I want to change part of it it becomes time consuming.

Hence, ability to copy & paste to dynamic editor would be nice.

I encountered this trying to paste to html editor, but overall it would be really nice if I could do this for every dynamic expression like I have chain 5 dynamic expressions, current user’s number is 1 or current user’s number is 2 or current’users number is 3, I copy this paste this to my notepad, replace the 2nd part with first part, and paste it to the editor.

Use cases like that

[rpetribu]

The forum is the environment where people who truly enjoy Bubble are. Helping, sharing, creating, collaborating… It’s really great to see you all listening to us here on the forum.

[asked111]

Just trying this new version. One thing that instantly jumped out at me is the wasted space on the states panel between the checkbox and the trash icon. Wouldn’t it be better to make the Name/Type fields wider so we can see more of the text? (or columns resizable)

[xstriker14x]

When will the opt-in be available for the rest of us? I’m not seeing it in settings at the moment and a lot of these changes look fantastic.

[maxencepautre]

Hey ! Great update. Few problems though:

• I’d like to access again the rich text options in all text datas. Usefull when dealing with adding CSS for instance
• The “dynamic data” button is sometimes annoying, poppin here and there. Not as fluid as before
• MAJOR PROBLEM: the processor of my computer is reaching 100% waaaay faster than without the beta display. Deal breaking situation here.

[asked111]

Had to switch this off again as just so many bugs and annoyances. When i get some time I will go through them and write them down to feedback constructively.

The biggest annoyance by far is how the property editor keeps vanishing and the page i’m working on jumping around to new location. Worse on smaller laptop screen of course. Maybe there’s a way to fix it in place that i missed?

Anyway back to the old property editor for now (which is SO much nicer on the eyes too tbh) will try again in another week.

Cheers

[thomas.labregere]

Bug report : Clicking errors no longer jumps to the problematic field (UX regression?)

Hi !

First of all, thanks for the work on the new Property Editor — lots of promising ideas in there

One thing I noticed though feels like a UX regression around error handling.

In the previous editor, clicking an error in the issues panel would:

• Take you straight to the field causing the issue

• Visually highlight it (red outline), so you instantly knew what to fix

In the new Property Editor, when I click an error:

• Nothing happens (frequently just reload)

• There’s no visual indication of where the problem is

This means manually hunting for the issue, which can be quite frustrating and time-consuming.

Have you had this type of feedback?