This is confusing to explain in words, but the panel setting I describe below is very unintuitive to me. Just a small navigation improvement idea. Issue: If I am looking at an entity, or to-many view, expanded with a collapsed panel on the left Then click on an item to open up its page on the rig…

I agree, this contributes to it feeling kind of wonky/buggy/inconsistent.

I was just about to create a request for this and stumbled upon this topic! As of this week’s release, Fibery now remembers the visual state (collapsed/expanded) of the fields column per user, per entity which was one of the two most annoying and confusing UX quirks that was driving our team crazy.…

[image] interr0bangr: The second and arguably even more annoying thing is what other people here have already mentioned. If 3 or more entities are open and the screen is split 50/50, Fibery will inexplicably auto expand the collapsed entity to the left if the entity to the right is closed when i…

Yep, exactly. Current: aBC (A 0%, B 50%, C 50%) --X (User closes C) AB (A 50% / B 50%) Expectation: aBC (A 0%, B 50%, C 50%) --X (User closes C) aB (A 0%, B 100%) The same applies to the other direction as well. Current: ABc (A 50%, B 50%, C 0%) X-- (User closes A) BC (B 50% / C 50%) Expecta…

What would you say in a slightly different use case: AA (user opens B) AB (user expands B) aBB (user opens C) aBC --X (user closes C) What should the panels’ state be in this case? I know this is ultra boring so thanks for bearing with me :sweat_smile:

when AA (A 100%) and (user opens B) then AB (A 50% / B 50%) when AB (A 50% / B 50%) and (user expands B) then aBB (B 100%) when aBB (A 0%, B 100%) and (user opens C) then aBC (A 0% / B 50% / C 50%) when aBC (A 0% / B 50% / C 50%) and (user closes C) then aBB (A 0% / B 100%) The key for me is to …

Ok, with the last use case we are on the same page :tada: This is not how it works right now but we are looking to tweak the behavior. [image] interr0bangr: The key for me is to never expand something that is collapsed, UNLESS THE USER EXPLICITLY SAYS SO. Now keeping the principle in mind l…

[image] antoniokov: So the result should depend on whether it was the user who initiated a to be collapsed. If we automatically collapse a to clear space for C it only seems logical to me to automatically bring a back when C is closed back. Would you agree? I don’t agree, because a user clos…

Gotcha. [image] interr0bangr: B was already open at 50% so you can assume the user still wants to see B and therefore I would expand it to 100%. This is not what we’ve seen so far during our UX tests. We’ve received a few complaints and noticed confusion about the aBB → aBC → AB case but not…

Closing Panels on Full Screen

Ideas & Features

interr0bangr March 5, 2024, 8:14pm 22

Paging @Yuri_BC because I think this conversation is related to your request here

Topic		Replies	Views
[DONE] Multi-panel context-preserving navigation Ideas & Features navigation	50	3583	April 12, 2022
CHANGELOG: June 9, 2022 / Publish Space to Web, Pin Checkbox and Formula Fields Changelog	12	839	June 15, 2022
[DONE] Autocollapse Spaces in sidebar Ideas & Features left-menu	17	717	January 23, 2025
[CLOSED] How to close out of "open as view"? Ideas & Features	25	2922	November 11, 2020
August 28, 2025 / 🧀 Create automation rules or buttons with Fibery AI (beta), improved Board View Changelog	49	930	September 4, 2025

Closing Panels on Full Screen

Related topics