mirror of
https://github.com/open-webui/pipelines.git
synced 2026-11-05 01:37:24 +00:00
[GH-ISSUE #270] Support for Collapsible Details in Markdown #128
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
open-webui/pipelines#128
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @sawallesalfo on GitHub (Sep 24, 2024).
Original GitHub issue: https://github.com/open-webui/pipelines/issues/270
While OpenWebUI claims to support full Markdown and LaTeX, collapsible elements like
<details>and<summary>do not render properly. This limitation restricts our ability to present additional information in a clean and organized manner. Here is a code example showcasing the intended functionality(main part in the method pipe):Here is an example of pipeline that I execute
When lauch pipelines, I got the output below that I got unexpected format
Would it be possible to enable support for collapsible details within Markdown? This feature would greatly enhance the user experience in chat conversions.
@thiswillbeyourgithub commented on GitHub (Sep 24, 2024):
On a somewhat similar line, but a tad more technical, I asked for persistence of emitters. Basically the UI change would be that the latest received status emitter would have an arrow that when clicked would display the list of emitters received.
Here's the link : https://github.com/open-webui/open-webui/discussions/5026
But to stay on topic: I too think it would be good to support collapsible details. I could use this to automatically hide the "thinking" xml tags of my claude sonnet output for example.
@drorm commented on GitHub (Nov 29, 2024):
And even better would be a solution where the details are not in the dom, but in local storage. There are 2 issues here:
Previous comments solves the first, and this approach solves the second.
@sawallesalfo commented on GitHub (Feb 20, 2025):
Possible with OpenWebUI version 0.5.10.
The details section should be before the output. It works like a reasoning block. For more details on different possibilities, refer to this link.
Here is a simple echo pipeline that works