If you’re entering a static value for colors, you need to click the “make static” icon on the right, right now it’s dynamic.
For the other bugs, can you please submit a bug report or DM an app ID and instructions on reproducible behavior so our team can take a look to understand what may have gone wrong?
@lindsay.esterman I won’t do a big report. The amount of time wasted trying to get past the bubble bot and the first layer of the support team is ridiculous. So this is the only place I will try to help you at. Take it or leave it. I’m trying very hard to use the new editor for you guys before the real launch. There are still many issues that I need to switch to the old editor to fix. I’ve been using bubble since 2016, I hope my feedback is valuable to you guys, but I’m just not going to do bug reports any more.
@Emmanuel I really hope you consider this feedback about the way support tickets are being handled. There are so many bugs that I don’t even report now because of this issue. There has to be a better way. Especially for specific beta testing and important new changes like the new editor design. Without knowing about all of these bugs, because no one wants to take the time to report them, you will think that everything is working great. In reality, there are a bunch of bugs that no one wants to report because they know what a pain it is to do so.
Right on! I’ve said it in the past, and I’ll say it again: There should be a Bubble resource who’s responsible for the intake/triage of all issues reported via all channels without having to jump through all the hoops. And it should be done with open arms and encouragement to engage in the channel of choice for the user, not for the product team.
You mean, a narrowly scoped job, which involves reading lots of text, and processing it into useful, structured information? I do wish there was a way to do that cheaply at scale.
In the old editor, that’s how my colors are setup for this element. When I switched to the new editor, the color values are different. That’s the issue. @J805 and I reported the issue with screenshots and a detailed breakdown.
Hey, I really personally appreciate the feedback you’re sharing about the new PE 
but I’m not able to reproduce this on my end, so we don’t have a consistent bug we can log and fix yet (properties disappearing from old to new PE). That’s why an app ID to repro would be massively helpful for our engineering team (and like I said, DMs are totally fine!).
Totally hear your frustration though, and only if you ever have the time and still feel like sharing more feedback, I’d love to get on a call.
Lol. Touché.
Please back the gray one, this new its no fluid, looks like a old wordpress. and has bugs like back de conditionals dosent work more. please plase, this was fixed and has to much clicks to do things
Here is another issue. Maybe a screen recording will help? It keeps closing out on me when trying to choose an icon.
Hey @lindsay.esterman! I’d love to try the new editor. Can you add me to the test group? thanks so much!
Hey guys, been using the new editor quite a while… Loads of good aspects but some real pain points. I think this one is one of the most annoying:
The issue is simply how easy it is to completely ruin text or expression in the new dynamic editor. a couple of misplaced (or mistimed) mouse clicks and the expression is turned to mush. Then pressing delete to try to pull it back together and all kinds of chaos ensues. Happens WAY too often for me.
If you could give this areas some attention that it would be much appreciated.
Another bug, I’m hoping this one should be easy to fix since it is obviously wrong.
There is a button that no longer works in the new editor. The button for backend workflows ‘Modify Types’ only works with the old editor. The new editor looks like the same action as ‘Detect Data’. This one is important. Hope you guys can fix it. 
It’s exactly same bug what I also reported at the mobilebeta board. Please check this post and you could check video report.
This makes users very annoying… T_T
Hey @lindsay.esterman , just wanted to follow up here. I’m new to the forum, but I’ve been on bubble for 6+ years, with multiple apps. thanks!
Working on a fix!
Hear you, we’re working on this right now with some new designs to access dynamic data.
Ah, thanks for reporting!
Yep, working on it now 
DM me your email!
Thanks for the response.
In the new property editor, we cannot set Max Width or Max Height to infinite (∞) inside conditional statements.
Put 0 when I remove the value, like below
I would like to understand why the navigation buttons—next, previous, first, and last—were removed from the new editor. These buttons were incredibly useful for making minor adjustments, as dragging elements sometimes causes them to move to unexpected locations. Could you please consider restoring this functionality in the new editor?
Yes, please @lindsay.esterman …users who want hot keys can use them, users who want buttons can use them, users who want to drag and drop in elements tree can drag and drop.
I use those buttons every single time I need to move something. Such a simple concept that provides enormous user benefits.
The new editor should be more flexible, not more restrictive
The hotkeys don’t even work 100% of the time. They almost always work, but sometimes randomly don’t. The buttons always work. I use them as a fallback.
