Address issues with content space for users on the default "Fixed" layout
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Context
Upon the launch of the file tree browser, users on widescreen monitors are continually giving Source Code feedback about the width of their repository content.
From data that @nickleonard pulled, 99.54% of users are on the default Fixed layout. It's very likely users just haven't bothered to change the default setting, or know the Fluid layout even exists.
There was discussion with the design team #23189 (comment 3003750736) about changing the default to Fluid but this wouldn't work for all products:
I think the biggest problem with defaulting to
fluidis that the experience of descriptive text such as in the description or comments is very poor at large size.
User feedback
See Feedback: Repository file tree 🌳 (#581271)
I find that whilst the file navigation now aligns to the user preference setting of fluid VS fixed width (!220811 (merged)), I much preferred when it didn't
😅 I mean, I use fixed width layout because it's much better (for me) to have a look at issues, MRs discussions, etc., but when looking at code it's a completely different thing hand taking advantage of the full width it preferable.
The MR "changes" tab also forces the fluid layout
🙂 I am not suggesting to revert back to forcing a fluid layout while navigating the files tree, but I would introduce a different user preference only for the layout of "code" pages
🙂
How can I get rid of this unused space ? Also, on right side is much space wasted if Duo isn't shown
...
I changed it from fixed to fluid - I'm happy now :-) Thank you !
Why is there so much padding on the left side of this file list?
I’m using a 27‑inch monitor, but the GitLab interface doesn't fill the screen. Could you please check this display issue? I’ve attached a screenshot for reference.
Why so much whitespace either side of the nav/file-content ... surely this is 2026 when an 80 column screen is the exception rather than the norm.
The code viewer is too small; there is always horizontal scrolling and nothing can be read comfortably. There is plenty of empty space on both sides, but the component doesn’t scale properly and doesn’t allow resizing.
The tree works better, but the overall experience is very poor and highly impractical. Simply increasing the size back to how it was before would be enough. As it stands now, it doesn’t make sense, since you’re trying to navigate code that you can’t properly read. I’ve switched to the integrated VSC because in its current state it’s not usable.
New file tree is ok, but monitors a wide, and it eats code wideness.