Could use some polish.
@lindsay.esterman If the team is pushing for everyone to use this editor, a constant 1-3 week update to this editor are needed. I love the direction + features and would love to use this daily, but there’s moments I have to revert.
I think they have been doing constant updates since at least December 2025 Property Editor Beta Update #1 so I’m not sure if all this needs is 1-3 more weeks if it’s still not polished and working as expected by now.
@feefeed I’ve seen this behaviour as well.
A small thing: I have images set up for profile pictures (a pretty common thing to do) and I run it through imgix. The old editor allowed me to set properties to find the face and add padding so the image displays properly. It’s gone now and I can’t seem to control how a profile image is rendered in the container now.
Hi, thanks for flagging and we’re shaping a fix now.
It’s in the gradient tab. We’re shaping to make more intuitive.
Adding a fix
Yes, would love to help you do this in the future! For now, we want to keep the beta toggle prominent to collect feedback.
Oh no, what’s your app ID and do you remember what actions got it into this state? Starting a DM.
Adding a fix, this is a Safari-specific bug. Sorry for the trouble!
The setting for adding padding around the face appears when you hit auto-crop around the face!
I couldn’t find the aspect ratio option for the image element with the new property editor. I had to go back to the old editor to setup that.
There is always contrast issue with this team, border colors, placeholdor colors etc
Submitted a bug for this - they are working on it.
I think the toggle represents the default (you’ve set it to yes)
@lindsay.esterman I think pretty much nowhere in Bubble uses a toggle to represent yes, it’s always a dropdown, this would make sense here
To me that icon works same as
for yes, and
for no. Or green light red light. Should be removed.
Thanks @lindsay.esterman! Looking forward to the adjustments. Definitely look into how Figma handles this section.
@lindsay.esterman Is there an option to change the canvas background color? My pages have dark backgrounds but it still has the bright canvas background.
Also I agree with @randomanon it needs to be more of a charcoal. the dark is too dark ![]()
I’m honestly not sure why:
- More users aren’t calling this out.
- Why it’s being ignored by the product team.
I literally get lost and overwhelmed when I toggle dark mode on, it’s that bad. Weirdly enough they already figured this out 10 years ago during the initial design of the property editor, I’m not sure why they would introduce a regression like this.
When using the new redesigned property editor, it really slows me down.
The loading and navigating performance of the whole editor is just really slow for my app.
I also had this in my app with the old editor but I used “issues_off=true” and it was REALLY FAST after it. However, this is not working any more in the new redesigned editor.
Any tipps to speed up the experience?
Two small pieces of feedback (although overall, happy with these updates. Takes some adjustment to re-learn where things are, but happy to roll with the bumps!)
1 - If we want to set a single border, we have to first set ALL borders on and then deselect individual borders. Adding a lot of clicks compared to the old flow (set borders individually → format chosen border)
2 - Could we have an ability to change change the default for how padding and margins are set? It’s minor, but I use inconsistent padding / margins a lot, and its adding extra clicks every time to swap from vertical-horizontal only to the 4 directions
Per support the missing time zone features should be fixed.
It’s disappointing to see a new version being pushed on users when it breaks functionality that already worked in the previous one.
It reminds me of the Table element, which was also released prematurely, full of bugs, missing essential features, and then seemingly abandoned. Nowadays, hardly anyone talks about it anymore, and most experienced Bubble developers still rely on repeating groups instead.
Just the other day, I helped someone here on the forum troubleshoot an issue where a Table element was displaying records that had already been deleted from the database. We spent hours trying to figure out what was going on. It was only after we replaced the Table with a Repeating Group that everything started working correctly.
Bubble really needs a stronger and more effective QA process.





