Entity view seems to be unnecessarily limited for max-width, and it prevents seeing all columns of wide collections table views:
2 Likes
This is by far my biggest UI pet peeve. A full-width option could be the single biggest quality of life improvement for me, because right now I have to full screen almost every collection block.
Similarly, I don’t understand why the center to-many/collection column is wider when there are fields on the right column and narrower (but centered) when everything on the right column is hidden.
2 Likes
Yeah, can we have this addressed please? I love that Fibery can have a lot of contextual data shown at once, but it’s often harder than it should be to display it effectively due to inconsistent max-widths.
Because of the recent feature where you can display expanded field information in the header, I wanted to try to use a single column layout, but the max-width gets even smaller if you completely hide the fields column!
Fields column expanded:
Fields column collapsed:
Fields column hidden (by turning off certain fields):
4 Likes
I also mentioned this via Intercom a while ago. Then it seemed that I was the only one wanting this so I’ve made a hack for it (I link an entity with description for the user why/how you need to collapse the field colum for full screen width 
)
But would be great if that’s not needed anymore since it clutters the workspace.
1 Like
We will indeed address this as a part of Entity View improvements this spring. Thanks for the feedback and the screenshots!
3 Likes
Some big strides were made a few months ago but it seems like the momentum on this has slowed a bit lately.
Is there a plan for full-width consistency/parity across all fields so we can avoid janky layouts like this?
1 Like
We woud also love this. Currently our screens look like a Jenga tower 
There are no plans to add support for extra-wide (full-width) setting for ‘simple’ fields.
Really? Respectfully, it seems like such a massive UI oversight. The option to expand fields to full width (which I love) is then at complete odds with the option to add “simple” fields to the left column (which I also love) and it really sucks to have to pick one or the other to ensure an entity doesn’t look visually broken. You introduced both options around the same time so I always assumed they were designed/planned to work in tandem and that such a glaring issue was going to be resolved in a not-so-distant release.
To be clear, I’m not asking for simple fields to be able to literally expand to full width because I know that would require a complete redesign for some of them (like files), I’m just looking for the margins/alignment of all fields to be consistent. I’m ignorant to the complexity, but having the left margin of the widest field on an entity be inherited by all other fields that are visible seems like it would be the simplest solution.
1 Like
So in the image you shared, you want the ‘simple’ fields to be aligned left, even if they don’t become full width?
Yes, exactly.