So less than “@drixxon”?
2 Likes
If the headache has a description, jeez
For me, it doesn’t show elements that are set to not visible on page load which is really annoying because I have to set them as visible on page load to see or edit them and then remember to disable it again before pushing to leave. Absolutely dreadful.
1 Like
Here to echo the same as everyone else. One note is that if you are unable to select elements in your element tree, you can toggle on and then off the “Only Show Hideable” toggle to restore the element tree’s regular functionality.
1 Like
Dude, honestly, this editor sucks and it seems to only get worse.
- You can’t go half an hour without having to refresh the page, clear cache, bla bla bla…
- The expression builder crashes out of the blue. The WF tab prevents you from selecting WFs.
- The data tab has to be constantly refreshed to show the data.
- And a lot of other things that if you keep sending bug reports… my God.
It’s looking like a testing playground for interns, where people do what they want, release features without concrete tests, and fuck whoever’s working.
8 Likes
Intern part feels so true
I know you all know this, but folks should definitely be submitting bug reports, and for what it’s worth, I brought this thread to Josh’s attention.
11 Likes
Thanks @mikeloc . I have sent a bug report. Can 100% handle a bit of mess as it’s brought into 2023, but it’s currently nigh on unusable.
5 Likes
Bug reporting is the first thing we all should do.
But what we really need is some attention of Bubble engineers (or product owner/manager) here in the forum. Almost 2 days from the first post in this thread (not even mentioning other threads with same editor problems during this year) and we still don’t know if the team is aware and fixing issues. Feels like screaming into the void…
2 Likes
Thank you all so much for flagging this behavior. Our team is investigating the editor’s current performance and we will be sure to relay an update as soon as we can! So sorry for the inconvenience here. If you haven’t already, please submit a bug report with as much information as you’re able to provide.
7 Likes
Have submitted a bug report - just here to add to the frustration of others. Editor is pretty much unusable at this moment in time.
1 Like
This is so on point. The editor is functional enough to get things done, but all the 2 second delays start to add up over a work session.
All the mini workarounds start to add up over time, and though it’s not egregious enough to walk away from, it’s definitely teetering on the edge of insanity.
1 Like
Awesome
Please for the love of God during your testing, load an app that actually has a production environment.
A fresh app, or hell, even a fully fleshed Zeroqode template is not at all indicative of the experience that most of us have come to know.
If you really want to be amazed, try to load in a single page app 
1 Like
That’s great, but let’s be more productive, what as soon as possible mean? this week?next month?
Have you even start doing something about it?
Same here
True mania is restarting your whole computer because refreshing the page just isn’t doing the trick
The data tab treats me like I’m wrong for asking for data. I’ve just grown accustomed to setting very specific, filtered lists for my data tab in order to get to the user // result I want after a refresh
BROOO the new expression editor will literally jump itself to outside parenthesis causing me to have to reclick on the area I was editing. Sometimes it’ll autofill information and then get mad at me because the expression is wrong.
I love the parenthesis, but the new layout // new performance is becoming more of a drawback than anything.
Even the way the layout shows suggested results is lowkey worse than from before. I’m doing more scrolling and more typing to find the option I need.
Honestly, why is the expression editor even a group-focus menu? I have my editor tab in a locked position on the side of the screen, and yet, there’s still copious amounts of underutilized white space. Not every bubble app is a 100 zoom 1280 width page setup.
I like to edit in 650 77 zoom just because it’s faster and flexbox is magnificent at creating apps for varying screen sizes.
Imagine all the wasted white space I’d have if I was editing in 375 lmao.
Put the groupfocus menu on the side and extend the elements tree to take up more space.
While I’m whining, I’m even somewhat upset that the editor pane is this weird dark grey that doesn’t match any other elements whatsoever. It doesn’t even match the toggled grey color you get when editing a “gray” workflow.
If I work a 6 - 8 hour day, I refresh in between 10 - 30 times depending on what I am working with. If I am working with plugin elements, then it will be in the 20s or 30s because often times they refuse to load. I face countless bug when it comes to creating expressions and also switching from px to % sometimes creates an unclosable element on the screen.
I have already made bug reports, but honestly, the frequency of bugs is so high and it takes so long to make a bug report (you guys ask for way too much information, like, it’s not my job to be user testing for you…)
edit: I am happy to help sending a screenshot or two, but writing a “how to reproduce this bug” is not worth my time
6 Likes
Sometimes it’s easier to brainstrorm a workaround or just deal with it rather than filling out a bug report.
Is bubble really unaware that it takes a good 2+ seconds to switch from the editor tab to the workflow tab?
Regardless of PC Power or how much you’re switching back and forth, you mise as well just run the editor with issues off and defer elements on.
2 Likes
I also think the relationship between client (customer) and service (bubble) is becoming too blurry, and we are doing a lot of free work for them
3 Likes