mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 10:58:17 -05:00
[GH-ISSUE #7301] Persistent unaddressed UX issues: all empty lines erased from user prompts, expanding prompt box, nearly black scrollbar and corrupted text when rich text enabled #14694
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#14694
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 @rotemdan on GitHub (Nov 24, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7301
Bug Report
Installation Method
Docker
Environment
Open WebUI Version: 0.4.4
Operating System: Windows 11
Browser (if applicable): Latest Brave
Confirmation:
Expected Behavior:
UI should, for the most part work normally. UI issues should be minor.
Actual Behavior:
There are persistent UI issues that degrade the core experience, some are likely easy to fix.
Description
Bug Summary:
I already reported several UI issues, that I perceive as important, as discussions, almost a month ago:
Seems like very few people have reported duplicates these or upvoted them, and it's possible the discussions got lost in a flood of many other ones.
The issues still persist in
v0.4.4. I find it very odd that people don't find these issues more important. If I were developing a chat UI these would be high priority, since they relate to the core user experience, way before optional enhancements or more sophisticated features.I would also likely have disabled "rich text" mode by default since it doesn't work correctly with code blocks, and overall, for users who aren't aware of it, gives the impression the application being "buggy" or "broken".
I think maybe people tend to get excited and motivated by the "new/cool stuff", or their own unique needs or edge cases, and less about "the obvious/core stuff", which they may assume the developer is 100% aware of, for whatever reason. Some people also have bad attention to details, and would simply experience the software as "buggy" but not really consciously work out what it is that causes that "feeling". There are also plenty of ultra-technical users using
open-webui, that may not even notice UX issues (even obvious ones), or have very low standards of quality in regards to "presentation" and "aesthetics" (the kind that enjoy using command-lines and cryptic shell script because it makes them feel "cool").Reproduction Details
Steps to Reproduce:
Reproduction details are simple and are detailed in the individual issues.
Note
I would like to express huge gratitude for making a great, free to use application, which I personally use every day. It seems that new features are being constantly added (many of which aren't really essential, used or needed by many), which is great, but I'm not sure about the effort that would be needed to maintain all of them in the long run, and the amount of resources that would remain to allocate to maintain and improve the core experience.
If you think that pull requests are the answer, remember also that the more complex the application becomes, the larger the learning curve for making contributions, especially casual ones. I'd also suggest that the core experience should be maintained by the core developer(s) (not casual pull requests), but the unessential extras possibly more by the larger community.
I assume you would convert this to a discussion (like most issues that are reported on the main tracker), but I still felt I had to post it here, because I'm not sure that otherwise they would get the attention they deserve.