If you're facing issues with rich text input, you can disable it from the settings.
Originally created by @bgeneto on GitHub (Nov 15, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/6973
## Workaround
<img width="923" alt="image" src="https://github.com/user-attachments/assets/9cc222ef-1b28-48a1-aba6-c24761ec8e9b">
If you're facing issues with rich text input, you can disable it from the settings.
Encountering this on MacOS + Chrome also. Strangely, adding an additional line before adding the closing back-ticks retains the formatting.
<!-- gh-comment-id:2486855897 -->
@willdady commented on GitHub (Nov 19, 2024):
Encountering this on MacOS + Chrome also. Strangely, adding an additional line before adding the closing back-ticks retains the formatting.
It's not just code. Any preformatted text is mangled. For example, dashes used for list items are escaped with backslash. Blank lines are stripped. I turned off the whole rich-text input in settings to regain control over how my input is interpreted.
<!-- gh-comment-id:2495749881 -->
@robertvazan commented on GitHub (Nov 24, 2024):
It's not just code. Any preformatted text is mangled. For example, dashes used for list items are escaped with backslash. Blank lines are stripped. I turned off the whole rich-text input in settings to regain control over how my input is interpreted.
You can most definitely toggle the rich text input feature off as a workaround.
With that being said, a lot of issues here should be fixed with the latest dev, testing wanted here!
<!-- gh-comment-id:2495852439 -->
@tjbck commented on GitHub (Nov 24, 2024):
## Workaround
<img width="923" alt="image" src="https://github.com/user-attachments/assets/9cc222ef-1b28-48a1-aba6-c24761ec8e9b">
You can most definitely toggle the rich text input feature off as a workaround.
With that being said, a lot of issues here should be fixed with the latest dev, testing wanted here!
@Smiley-McSmiles commented on GitHub (Nov 24, 2024):
Personally I'm seeing many issues with rich/markdown text:
This is also fixed by going to bottom-left-user/Settings/Interface/Chat/Rich Text Input for Chat -> Off
<!-- gh-comment-id:2496023175 -->
@Smiley-McSmiles commented on GitHub (Nov 24, 2024):
Personally I'm seeing many issues with rich/markdown text:
This is also fixed by going to `bottom-left-user/Settings/Interface/Chat/Rich Text Input for Chat` -> `Off`
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @bgeneto on GitHub (Nov 15, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/6973
Workaround
If you're facing issues with rich text input, you can disable it from the settings.
@willdady commented on GitHub (Nov 19, 2024):
Encountering this on MacOS + Chrome also. Strangely, adding an additional line before adding the closing back-ticks retains the formatting.
@chip902 commented on GitHub (Nov 20, 2024):
This ^^
@robertvazan commented on GitHub (Nov 24, 2024):
It's not just code. Any preformatted text is mangled. For example, dashes used for list items are escaped with backslash. Blank lines are stripped. I turned off the whole rich-text input in settings to regain control over how my input is interpreted.
@tjbck commented on GitHub (Nov 24, 2024):
Workaround
You can most definitely toggle the rich text input feature off as a workaround.
With that being said, a lot of issues here should be fixed with the latest dev, testing wanted here!
@Smiley-McSmiles commented on GitHub (Nov 24, 2024):
Personally I'm seeing many issues with rich/markdown text:
This is also fixed by going to
bottom-left-user/Settings/Interface/Chat/Rich Text Input for Chat->Off