mirror of
https://github.com/open-webui/open-webui.git
synced 2026-06-09 11:45:57 -05:00
[GH-ISSUE #6580] issue/enh: incorrect input markdown #85151
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 @HeyThisWasRandomlyMade on GitHub (Oct 30, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/6580
Bug Report
Installation Method
Docker
Environment
Open WebUI Version: v0.3.35
Operating System: kubuntu 24.04
Confirmation:
Expected Behavior:
It should either format it into italics correctly or just not format any text in the message box into markdown at all until after you send the message.
Actual Behavior:
The text is bolded instead. It won't paste text with markdown in it on mobile. On mobile you cannot stop bold text from appearing after bolding it.
Description
Bug Summary:
Issue: Markdown italics is formated into bold in the message box. It interprets the asterisk into a double asterisk, making it bold. This also makes it impossible to paste something into the text box on mobile with markdown formatting already in it. If you're on mobile, it's impossible to stop text being bolded, meaning you have to edit the message after or delete all your work.
Reproduction Details
Steps to Reproduce:
Basically I'd like to fix this issue and make it an option to disable markdown in the text box and format it into it after sending the message or revert the change if it was unintended.
@ProjectMoon commented on GitHub (Nov 1, 2024):
Similar happens with predefined prompts. They're put into the textbox in rich text mode and then rendered incorrectly on output. Notable case is --- horizontal rule, which winds up as a H1 header instead because the blank lines are removed.
@tjbck commented on GitHub (Nov 24, 2024):
You can most definitely toggle it off the rich text input from the settings. I believe some of the issues here are resolved with the latest dev, testing wanted here!
Closing in favour of #6973