New updates to the redesigned property editor!

Hi everyone,

I’m Lindsay, a product manager at Bubble, here with another update on the redesigned property editor. We appreciate all the feedback you’ve continued to share and are excited to share what we’ve shipped this sprint!

UX and UI improvements

Constraints and Sort by are back inline. We removed the constraints and Sort by popovers so you can edit everything directly in place.

Constraints and Sort by are more user-friendly. We’ve added auto-focus, so you can start typing right away without clicking into the field, operator, or value. You can now also change a constraint’s field or operator without deleting and recreating the constraint. And the new drag-and-drop behavior introduced in a previous update remains. You’ll see these improvements in places like Do a search for, :filtered, and :sorted.

Inputs that allow dynamic data will now be full-width. Previously, many inputs were crammed to the right, making long expressions hard to read. We fixed that by making them stacked and full-width.

Custom states are back inline. We removed the popover for setting a custom state so you can edit it directly in the property editor, reducing clicks, mouse, and eye movement.

Bug fixes

  • The icon popover will no longer close when changing icon libraries
  • Nested popovers will no longer randomly snap to the top left corner rather than being anchored to their parent
  • Deleted fields will no longer be added when selecting “add all fields”
  • You can now set a background color to ‘none’ in the styles tab conditional menu (and we’re currently adding this back for element conditionals)
  • Toggling “Visible on page load” property will remain as you initially set it when updating its value in conditionals
  • Rich text editor properly syncs with field values like in the Send Email action
  • The issue checker will no longer incorrectly flag a ‘type required’ error in the choice popover
  • Privacy rule expression text will no longer appear white and low-contrast with the new PE enabled
  • Clicking into dynamic data will no longer close the background popover ‘gradient’ tab or ‘background’ tab
  • Clicking into dynamic data will no longer close the border style color in the conditionals tab
  • Clicking a color variable will no longer close the individual borders popover in the styles tab
  • The “Appearance” section will always show for the reveal element of the “Reveal & Hide Password” plugin
  • The “Size” section will always appear in the Visual tab for user-built plugins
  • Row gap can now be removed as a conditional property
  • The alignment property is now changeable in the conditional tab
  • The “MISSING” conditional property from an AI generation error can now be removed
  • Conditionally defining static images will no longer produce a rendering error
  • Picture uploaders now support the ability to add dynamic data for its initial content

Coming soon

We’re removing the dynamic expression popover, putting workflow fields back inline, and improving the process of adding dynamic data (no more tiny plus icon).

Thank you again for the feedback and please keep sharing! I’ll be back with another update soon!

Lindsay

21 Likes

Good job!

1 Like

Thanks for the updates.

Just one question @lindsay.esterman, what does that “Add all states” section do?

I mean, for fields it’s correct to say that “Add all fields” makes sense, since the system knows which fields exist in the “thing”.

But regarding custom states, there’s no way to know which states the user intends to create. Or am I missing something here?

For some reason this morning I no longer have access to the Beta Property Editor? Did something change? @lindsay.esterman

That button is a shortcut to add all the states as dropdowns so you can set values for many of them at once, instead of having to click the plus icon for each one you want to change. It’s not intended to create many custom states, but to set many state values based on the workflow goals (an accelerator).

No, that’s very strange… sorry about that. DM me your email and I can add you back!

1 Like

Great update @lindsay.esterman, however:

I don’t know what you all did recently but privacy rule expressions using parentheses no longer get highlighted appropriately. This old “white low-contrast” highlight is exactly what I describe here:

Whatever change you made stopped this feature from working properly. Please fix this as it can inadvertently lead to severe security issues with users’ apps.

1 Like

Shouldn’t this be red if there is an error? Right now, you have to click into it all the way to see that it has an error.

Or at least automatically open to the error like it used to do here so we know where the issue is, its obvious and in red:

This is what it looks like when we click on the error with the new editor, doesn’t show anything in red.

2 Likes

I can see and feel the improvements. Thank you. :blush:

Small bug here. It looks like this input field for an Alert should either not show up by default or the toggle ‘change the alert message’ should be toggled to on by default. It doesn’t seem to be consistent when it first shows up. Obviously there is a work around, but just thought I would point it out.

See video below:

1 Like

Hey, I’m sorry but our work was not related to that. The text was appearing white on a white background so we just changed the text color, and this was only occurring when the new PE was enabled.

Thanks for pointing out! There are a couple error states we missed highlighting in red or don’t open properly. Adding this to the list.

Thank you for your feedback!

Good catch, thank you!

2 Likes

I also really enjoy being able to add a new field in a workflow but it doesn’t seem like we can do that anymore. You have to go to the database to do that now.


Side note:
You guys should also be counting every time we turn of the new editor. Might give you a good indication on how many bugs are left if we have to turn it on and off each time to fix and issue.

Also, If you are counting how many apps actually have this on, you will have a very skewed number since I have 200+ apps but I don’t open all of them anymore, some are just old projects or test projects that the new editor might be enabled on but I’m not even using it there.

Looking forward to trying these out!

2 Likes

Looks like I can’t choose a color now for some reason. :grimacing: @lindsay.esterman

Hmm ok, well thanks for letting me know either way.

Also, I have asked a few times, but what do you think about the following?

1 Like

Great updates!

A small request: add the documentation back

2 Likes

The new editor was being so slow & sluggish for me this morning I reverted back to the old one. However I then noticed this update was released so switched back, and the sluggishness has fixed.

So, if anyone is finding the property editor extremely slow and laggy, try reverting back to the old one and then back to the new one again… should fix it. :+1:t2::crossed_fingers:t2:

Operators disappear when switching to the new editor.

1 Like

Is it actually missing (issue checker shows a problem) or just visually missing? If the former, this is so dangerous, imagine switching to the new editor and your app randomly stops working.

Just visually missing.