mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-07 11:28:35 -05:00
[GH-ISSUE #750] Output limited to a very narrow collumn - text squashed and screen realestate wasted #12202
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#12202
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @sammcj on GitHub (Feb 16, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/750
Bug Report
Description
Bug Summary:
The application seems to limit the width of the chat conversation to a very narrow column.
This makes for excessive scrolling and makes reading code difficult.
Steps to Reproduce:
It appears be be hard coded like this so I think everyone would experience it.
Expected Behaviour:
The width of the conversation area to scale horizontally to the available display size + a little padding.
For example, perhaps it could always be about 80% of the available space between the side panel the the scrollbar?
Otherwise - an option to set the maximum width in settings would be great.
Actual Behaviour:
Text is squashed into a tiny little column in the centre of your browser window.
This might be OK for a mobile device but is very hard to work with on a standard 4k screen.
Environment
Reproduction Details
Confirmation:
Logs and Screenshots
Browser Console Logs:
N/A (I think), but just let me know if you'd like me to provide any of the calculated CSS/HTML and I'll add it.
Docker Container Logs:
N/A (no errors)
Screenshots (if applicable):
Installation Method
Docker
Additional Information
Note
If the bug report is incomplete or does not follow the provided instructions, it may not be addressed. Please ensure that you have followed the steps outlined in the README.md and troubleshooting.md documents, and provide all necessary information for us to reproduce and address the issue. Thank you!
@justinh-rahb commented on GitHub (Feb 16, 2024):
I do commend you for giving a detailed report, we love to see those and I hope to see more like it, thank you. If I could kindly suggest, please review past issues or discussions in the future before opening new ones as we have a couple matching this one:
Duplicate issue #711
Fixed in PR #744
@sammcj commented on GitHub (Feb 16, 2024):
I did search through issues first.
Fullscreen mode doesn't fix it (and it seems to be a bit broken as well). Fullscreen seems to be on the other extreme end of the scale where it uses all of your browser which is overkill unless I guess you're running it full screen on a dashboard maybe?
What I'm proposing here is a responsive or at least configurable design.
Fullscreen looks like this:
@justinh-rahb commented on GitHub (Feb 16, 2024):
Fair, I agree fully on both of these, does look a bit whack at that scale either way currently.
@tjbck commented on GitHub (Feb 16, 2024):
Full screen mode disabled:
Full screen mode enabled:
Screenshot of WIP
@sammcj commented on GitHub (Feb 16, 2024):
Yeah sorry if I didn't explain it very well the first time - sometimes it's hard to describe in words 😅
@sammcj commented on GitHub (Feb 16, 2024):
What resolution / scaling is that at @tjbck?
@justinh-rahb commented on GitHub (Feb 16, 2024):
🥰 Oh Tim, my OCD would hug you but my ASD doesn't do hugs, they were doing a 2-for-1 deal on my birthday I guess
@justinh-rahb commented on GitHub (Feb 16, 2024):
My apologies @sammcj, with more context of your intention, your issue report is bang on. And now @tjbck has something to tag with his incoming PR 👍
@tjbck commented on GitHub (Feb 16, 2024):
@sammcj not entirely sure, but using a 33" ultrawide monitor with macos!
@justinh-rahb commented on GitHub (Feb 16, 2024):
@sammcj commented on GitHub (Feb 16, 2024):
woop woop, thanks folks - that was incredibly fast turnaround 😄 ❤️