mirror of
https://github.com/open-webui/open-webui.git
synced 2026-03-11 00:04:08 -05:00
Various usability issues with the rich-text editor (AKA rich-text is hard!) #2856
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/open-webui#2856
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 28, 2024).
Bug Report
Installation Method
Docker
Environment
Confirmation:
Screenshots/Screen Recordings (if applicable):
Suggestions
I'm not actually sure if the rich-text is still on by default. I generally have it off but I felt I could give useful feedback so I turned it on to see how it's progressing.
If I were developing this I'd simply have it disabled by default, mark it as "experimental", and not worry too much about trying to fix every aspect of it, at least in the short-term. If you have it as enabled by default, that may put you in a position where you may feel committed to spend an unreasonable amount of time struggling to get it to do everything correctly.
Users don't necessarily want it that badly (for example: ChatGPT doesn't have rich-text editing and I don't see users "protest" or complain on, say, reddit). Letting go of perfecting this would allow you to put your time and attention to other, likely easier, issues, with better effort-to-benefit ratio.
@tjbck commented on GitHub (Nov 28, 2024):
#6973
@rotemdan commented on GitHub (Nov 28, 2024):
Yeah, sure, I enabled rich-text to give useful feedback (not included elsewhere, as far as I know), but you just closed the issue? I guess you don't want any feedback about the feature?
@devanenWl commented on GitHub (Nov 28, 2024):
It's duplicated, he just closed it so it would be more easy to manage
@rotemdan commented on GitHub (Nov 28, 2024):
#6973 basically tells users to how disable the feature. I disabled it a month ago and enabled it now for the purpose of giving detailed feedback on particular aspects (a few that I could recognize quickly). #6973 is not the right place for that.
The title says "issue: rich text input" as if the feature itself is a problem (it doesn't say it's a "megathread" or anything like that). I don't think it's a problem by itself, is just has a lot of behaviors that don't work as well as most users expect, (basically can feel "buggy" and frustrating).
I care that new users, with the feature on by default (as far as I know) wouldn't have a good impression of the software. As long as the feature is on by default, it make sense to provide detailed feedback on it.
@devanenWl commented on GitHub (Nov 28, 2024):
Before being edited by maintainer, the original post has already mentioned the issue and its weird behavior, you can check it.
It's easier for maintainer to manage by close duplicate issues. Mine is also closed because of being duplicate lol
@rotemdan commented on GitHub (Nov 28, 2024):
It doesn't mention the particular set of issues described here (at least not all of them).
Anyway I just don't see how I could just paste this content there in one big message. It would feel inappropriate, suddenly putting on a lengthy, detailed, message on a thread that's basically just telling people to turn some feature off, where mostly people write very short messages. Would feel like I'm trying to "take over" that issue maybe. I don't know. Just trying to do the right thing.
@devanenWl commented on GitHub (Nov 28, 2024):
Don't worry, when somebody tags the issue, it will be logged in that issue so maintainer can revise later.
You did a great job by showing these stuff under GIF. Many thanks !!!