For me āCollapse if hiddenā should be checked by default
When we group a few elements in a group, the default height of the resulting group becomes the height of all the elements put together before we grouped them. But this is an annoyance. This means that even if elements within that group are hidden and hence collapsed, the group wonāt reduce in height below what it was set initially. It should just become as minimum height zero, I think.
But probably both of these might depend on peopleās preferences and I am not sure what would majority want.
Been asking for years hopefully they will get around to it
Been asking since the flexbox was first introduced, hopefully they will get around to it
Same, asked since flexbox first introduced, hopefully they will get around to it
Should not default to primary color, should default to white or transparent as it doesnāt really serve users much as most developers that want to show progress do so in other ways
Definitely do not make this enabled by default, it is an experimental feature. I personally do not use it, and Iād hate to be forced into using something I have no need for
Yes
Yes
Keep it as not checked since not all sites want to be exposing their site map as not all apps are concerned with SEO, and for developers that are delivering more complex SEO abilities via their sitemaps, they generate their own, especially the case in multiple language apps that require SEO in multiple languages, and the sitemap file is not just links to pages, it uses the links from the data types those pages are the content type of via the built in ālinkā field for any data type that is set to the content type of a page or multiple pages, which would imply I believe that any data that is not exposed publicly or has privacy rules are not accessible via the sitemap even though the page might be.
This is crazy to me, canāt even imagine writing most of my expressions without fine-tuned control over ORs and ANDs. I really genuinely am curious how itās even possible to build an app without the parentheses.
Me too I know experimental features shouldnāt be enabled by default, but my point is that this feature is clearly no longer experimental if itās been around for two years and was part of their expression composer overhaul (which they later backtracked on unfortunately even though it was a step in the right direction despite its flaws)
It is definitely weird to keep calling it experimental. Itās like theyāre not really happy with its behavior but also donāt want to fix it but they donāt want to get rid of it either because itās necessary. The thing about it is that itās at least stable and āwhat you see is what you get.ā If it breaks, it tells you that it breaks. They should definitely enable it by default in the short term but more importantly stop wasting time on the new workflow editor and give us a real working ābetaā expression composer that is fully modular and allows you to:
edit anywhere inside the expression without breaking the whole thing
find & replace expressions
copy/paste individual parts of expressions
As for boosts, my biggest one right now that is an eternal source of frustration: Please stop resetting the design tab every time we view backend workflows. Itās so annoying to keep having to navigate to the right element over and over again.
Another one, paste conditions in elements in a specific order instead of always at the bottom.
Iāll try to think of other boosts later but there are already some good ones here I agree with.
Iāve used the parenthesis feature on every single app Iāve worked on or built since it was introducedā¦ turning it on is the first thing I do when working on a new app.
I genuinely couldnāt even contemplate the idea of not using it.
It provides complete control of the order and grouping of operators in expressions - all of which is standard, fundamental programming logic which, without the use of parenthesis, you canāt do with Bubble expressions.
I canāt open more than one editor at a time. Even one crashes every few minutes for me because of high memory consumptions.
Earlier I used to have one tab for live and one for dev. But now I am limited to one and a lot of my time gets wasted in just switching from live to dev and vice versa. Plus refreshing the page every few minutes because it crashes or becomes unresponsive.
Me too, since every time Iāve seen a Bubble dev post in a forum that their changes werenāt saved, it was because they had multiple editor tabs open. (Iām sure it can happen for other reasons, too, such as network glitches or computer problems, but this has been the pattern Iāve been seeing.)
When adding an API connector call, the default should be action and not datasource. I pretty much NEVER use datasource, since it doesnāt give any control over when it gets updated and you can accomplish the same thing with actions + page states.
Excellent suggestion, probably best one yet. I also never really use datasource for same reasons you outlined.
Sounds like I might need to reinvestigate this. Do you have any screen shot of an expression you use this for that is not possible to be done with multiple conditions that are order properly for execution from bottom to top?
The default width for a group is 40px with fit width to content unchecked. This is a significant improvement over what it used to be, which was 200px with fit width checked.
However, since fit width to content is unchecked by default (correct in ~90% of use cases) and I rarely use min-width with fit width to content, I find that I almost always clear that minimum width. It would save time to have minimum width unset by default. I typically also clear the min-height, but since fit height to content is checked in those cases, I understand why having a default min-height makes sense.
When creating a reusable element from an existing group with workflows that are grouped in folders please get rid of the folder name that it was in. Currently we get this error in the newly created reusable that says this folder name is not an option āxZuyGfā and if you check the name drop-down it is empty. So either create the same folders beforehand or at least empty this position.
I know experimental features shouldnāt be enabled by default, but my point is that this feature is clearly no longer experimental if itās been around for two years and was part of their expression composer overhaul (which they later backtracked on unfortunately even though it was a step in the right direction despite its flaws)
who at bubble chose 56px as the default height of a row when we uncheck fixed number of rows?