[GH-ISSUE #16612] feat: disable "Rich Text Input for Chat" by default because it corrupts input #17976

New Issue

GiteaMirror · 2026-04-19T23:52:51-05:00

GiteaMirror commented

2026-04-19 23:52:51 -05:00

Originally created by @understood-the-assignment on GitHub (Aug 14, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16612

Check Existing Issues

I have searched the existing issues and discussions.

Problem Description

Hi,

In our internal deployment of Open WebUI, we have received feedback that users are frustrated by the "Rich Text Input" feature. The problem arises when they try to paste text with special characters (e.g. program source code), which are then converted to rich formatting.

The "Rich Text Input" feature converts pasted characters from Markdown formatting to formatted text, and when the prompt is submitted, the formatted text is converted back to Markdown. However, this process is lossy, and can corrupt the user input. For example, _test_var = _foo_bar * _bar_foo * _foo_foo * _bar_bar is corrupted into _test_var = _foo_bar _barfoo_ _foo_foo * _bar_bar.

Desired Solution you'd like

I think we should mirror what chatgpt.com does, and not attempt to interpret user input as using any particular formatting syntax (Markdown or otherwise). As such, user-entered text should be always treated as plain text.

In practice, I think "Rich Text Input" should either be disabled by default, or there be a global (site-wide) setting which disables it.

Alternatives Considered

Some alternative ways to approach this could be:

Have the Rich Text Input feature somehow detect when the user is pasting code.
Have the Rich Text Input perfectly preserve formatting characters, so that even if they're interpreted as Markdown, the model can see the exact pasted string when the message is submitted.
Make it easier and straight-forward to paste code as a code block (e.g. typing ``` is not discoverable for people not versed in Markdown or not expecting typed text to be formatted as Markdown).

Additional Context

No response

Originally created by @understood-the-assignment on GitHub (Aug 14, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16612 ### Check Existing Issues - [x] I have searched the existing issues and discussions. ### Problem Description Hi, In our internal deployment of Open WebUI, we have received feedback that users are frustrated by the "Rich Text Input" feature. The problem arises when they try to paste text with special characters (e.g. program source code), which are then converted to rich formatting. The "Rich Text Input" feature converts pasted characters from Markdown formatting to formatted text, and when the prompt is submitted, the formatted text is converted back to Markdown. However, this process is lossy, and can corrupt the user input. For example, `_test_var = _foo_bar * _bar_foo * _foo_foo * _bar_bar` is corrupted into `_test_var = _foo_bar _barfoo_ _foo_foo * _bar_bar`. ### Desired Solution you'd like I think we should mirror what chatgpt.com does, and not attempt to interpret user input as using any particular formatting syntax (Markdown or otherwise). As such, user-entered text should be always treated as plain text. In practice, I think "Rich Text Input" should either be disabled by default, or there be a global (site-wide) setting which disables it. ### Alternatives Considered Some alternative ways to approach this could be: - Have the Rich Text Input feature somehow detect when the user is pasting code. - Have the Rich Text Input perfectly preserve formatting characters, so that even if they're interpreted as Markdown, the model can see the exact pasted string when the message is submitted. - Make it easier and straight-forward to paste code as a code block (e.g. typing ```` ``` ```` is not discoverable for people not versed in Markdown or not expecting typed text to be formatted as Markdown). ### Additional Context _No response_

GiteaMirror closed this issue

2026-04-19 23:52:52 -05:00

GiteaMirror commented

2026-04-19 23:52:53 -05:00

@tjbck commented on GitHub (Aug 14, 2025):

You can disable it from interface settings.

@tjbck commented on GitHub (Aug 14, 2025): You can disable it from interface settings.

GiteaMirror commented

2026-04-19 23:52:54 -05:00

@understood-the-assignment commented on GitHub (Aug 14, 2025):

You can disable it from interface settings.

Thank you, how to do this for all users (globally), please?

@understood-the-assignment commented on GitHub (Aug 14, 2025): > You can disable it from interface settings. Thank you, how to do this for all users (globally), please?

GiteaMirror commented

2026-04-19 23:52:55 -05:00

@m3ngyang commented on GitHub (Sep 21, 2025):

You can disable it from interface settings.

hi, how to disable it? @tjbck

@m3ngyang commented on GitHub (Sep 21, 2025): > You can disable it from interface settings. hi, how to disable it? @tjbck

GiteaMirror commented

2026-04-19 23:52:56 -05:00

@rgaricano commented on GitHub (Sep 21, 2025):

User Settings/Interface/Input section

@rgaricano commented on GitHub (Sep 21, 2025): User Settings/Interface/Input section

GiteaMirror commented

2026-04-19 23:52:57 -05:00

@rbsn-cpu commented on GitHub (Dec 11, 2025):

how for everybody ?

@rbsn-cpu commented on GitHub (Dec 11, 2025): how for everybody ?

GiteaMirror commented

2026-04-19 23:52:58 -05:00

@aberios commented on GitHub (Jan 3, 2026):

You can disable it from interface settings.

The original question was whether this can be disabled globally for all users by default (though it would make sense to allow users to override and enable it). The current behaviour of enabling by default is contrary to what most users are familiar with when using other GPT clients, and primarily caters to technical users who are familiar with markdown.

@aberios commented on GitHub (Jan 3, 2026): > You can disable it from interface settings. The original question was whether this can be disabled **globally for all users** by default (though it would make sense to allow users to override and enable it). The current behaviour of enabling by default is contrary to what most users are familiar with when using other GPT clients, and primarily caters to technical users who are familiar with markdown.

GiteaMirror commented

2026-04-19 23:52:58 -05:00

@Classic298 commented on GitHub (Jan 3, 2026):

@aberios

https://github.com/open-webui/open-webui/pull/19954

@Classic298 commented on GitHub (Jan 3, 2026): @aberios https://github.com/open-webui/open-webui/pull/19954

GiteaMirror referenced this issue

2026-04-20 05:30:13 -05:00

[PR #17976] [CLOSED] FIX: N+1 database query in feedbacks #24624

GiteaMirror referenced this issue

2026-04-25 12:39:34 -05:00

[PR #17976] [CLOSED] FIX: N+1 database query in feedbacks #40254