While testing the RC2 version, I came across several bugs and potential improvements:
Bug: The last dynamic data item in the full-screen code editor is partially hidden. bug_last-item-half-hidden
Bug: In the full-screen code editor, the buttons for dynamic data and variables disappear after switching to variable search. bug_missing-buttons-fullscreen-code
UX Improvement: The floating settings (e.g., background, typography, transform) overlap the search bar. ux_options-overlapping-search-bar
UX Improvement: In the STYLE tab, you’ve implemented the “accordion category pinned to top” behavior, could the same be applied to the CONTENT tab and Page Settings? Not to hide other categories, but just to keep the selected one fixed at the top. Now it’s impractical because when you scroll down in one category you have to scroll up in another. ux_fix-category-accordition-to-top
UX Improvement: Wouldn’t it be better to deselect the category in STYLE tab when switching between elements? ux_deselect-style-options
Bug: The structure panel is still a bit buggy. More accurate compared to version 1.12.4, but still not ideal yet. buggy-structure-panel
UI Improvement: Design idea for a structure panel menu that aligns with the v2 style, dark mode and better color contrast for light mode. I can then send you what I’ve changed, if you decide to implement it. new-structure-panel-menu
UI Improvement: Would you consider darkening the backdrop color in in-builder popups? In dark mode, you will not be blinded (especially at night) and in light mode it still looks good. dark-backdrop-design
Not RC related but height value “100%” doesn’t work inside carousel. Is this expected? For example, 100vh works fine. Use case: I want to put carousel inside section which has set height and want to fill that section with carousel.
That’s everything for now!
Could you please discuss these points with the team, especially the UX/UI improvements?
It would be better if you created a separate report for each problem, as we create a separate task for each confirmed problem so that we can mark the report as solved. If there are several problems in one report, this is almost impossible or it becomes confusing very quickly.
In addition, feature requests/improvements should be made in the appropriate category—ideally, separately from each other.
Why would it be better? I don’t see any advantage in this, especially since it looks “calmer” when the panel doesn’t change.
That’d be rather an improvement than a bug.
Could be considered a simple improvement. Let’s see.
Could be considered a simple improvement. Let’s see.
Carousel: yes, that’s expected since the carousel itself doesn’t have any height, so the 100% doesn’t have any reference point (“100% of nothing”). You can add a min-height to the carousel that equals the section height – then you can use 100%.
Hi @timmse!
Sorry about that, I’ll separate future reports correctly.
1. & 2. - Great. 3. - Thanks for clarification. 4. & 6. - Will create improvement requests. (active category fix to top & buggy panel) Carousel - Thank you, I understand.
7. & 8. - Should I also create a separate improvement requests for these? (darker backdrop & structure panel menu redesign) 5. - Maybe it’s a personal preference, but when changing an element, I’d rather select the option I want to modify right away rather than having to deselect the previous options.