github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-05-06 10:58:17 -05:00
Code Issues 1.3k Packages Projects Releases 126 Wiki Activity

[GH-ISSUE #22784] issue: [Sidebar] Chat Menu Dropdown Remains Open After Clicking "Clone" #35346

New Issue
Closed
opened 2026-04-25 09:34:15 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-25 09:34:15 -05:00
Owner
Copy Link

Originally created by @silentoplayz on GitHub (Mar 18, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/22784

Check Existing Issues

  • I have searched for any existing and/or related issues.
  • I have searched for any existing and/or related discussions.
  • I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!).
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.8.10

Ollama Version (if applicable)

v0.18.0

Operating System

Ubuntu 24.04.4 LTS

Browser (if applicable)

Mozilla Firefox Snap for Ubuntu v148.0.2 (64-bit) / Google Chrome v146.0.7680.80 (Official Build) (64-bit)

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

When clicking the Clone button in the chat's three-dots (hamburger) menu, the chat should be cloned, the user should be navigated to the new chat, and the three-dots menu on the original chat should close. This should match the behavior of other actions like "Rename" or "Archive" which result in the menu being dismissed.

Actual Behavior

The chat is cloned successfully and the user is navigated to the new chat, but the three-dots menu on the original chat item remains open in the sidebar.

Steps to Reproduce

  1. Open the chats sidebar and locate an existing chat.
  2. Click the three-dots (…) icon next to the chat title to open the dropdown menu.
  3. Click the Clone option.
  4. Observe that the app navigates to the cloned chat, but the menu for the original chat remains visible in the sidebar.

Logs & Screenshots

Screenshot showing the menu still open after cloning:

Image

Additional Information

The issue is located in src/lib/components/layout/Sidebar/ChatMenu.svelte. The cloneChatHandler() call in the button's on:click does not include a statement to set the dropdown's show state to false.

<!-- src/lib/components/layout/Sidebar/ChatMenu.svelte -->
<button
    draggable="false"
    class="..."
    on:click={() => {
        cloneChatHandler(); // Lacks show = false;
    }}
>

Adding show = false; after the handler call should fix this inconsistency.

Originally created by @silentoplayz on GitHub (Mar 18, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22784 ### Check Existing Issues - [x] I have searched for any existing and/or related issues. - [x] I have searched for any existing and/or related discussions. - [x] I have also searched in the CLOSED issues AND CLOSED discussions and found no related items (your issue might already be addressed on the development branch!). - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.8.10 ### Ollama Version (if applicable) v0.18.0 ### Operating System Ubuntu 24.04.4 LTS ### Browser (if applicable) Mozilla Firefox Snap for Ubuntu v148.0.2 (64-bit) / Google Chrome v146.0.7680.80 (Official Build) (64-bit) ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior When clicking the **Clone** button in the chat's three-dots (hamburger) menu, the chat should be cloned, the user should be navigated to the new chat, and the three-dots menu on the original chat should **close**. This should match the behavior of other actions like "Rename" or "Archive" which result in the menu being dismissed. ### Actual Behavior The chat is cloned successfully and the user is navigated to the new chat, but the three-dots menu on the original chat item remains open in the sidebar. ### Steps to Reproduce 1. Open the chats sidebar and locate an existing chat. 2. Click the **three-dots (…)** icon next to the chat title to open the dropdown menu. 3. Click the **Clone** option. 4. Observe that the app navigates to the cloned chat, but the menu for the original chat remains visible in the sidebar. ### Logs & Screenshots **Screenshot showing the menu still open after cloning**: <img width="395" height="338" alt="Image" src="https://github.com/user-attachments/assets/1535dc8a-17ec-49c7-a493-e792c4740df5" /> ### Additional Information The issue is located in `src/lib/components/layout/Sidebar/ChatMenu.svelte`. The `cloneChatHandler()` call in the button's `on:click` does not include a statement to set the dropdown's `show` state to `false`. ```svelte <!-- src/lib/components/layout/Sidebar/ChatMenu.svelte --> <button draggable="false" class="..." on:click={() => { cloneChatHandler(); // Lacks show = false; }} > ``` Adding `show = false;` after the handler call should fix this inconsistency.
GiteaMirror added the bugconfirmed issue labels 2026-04-25 09:34:16 -05:00
GiteaMirror commented 2026-04-25 09:34:17 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Mar 21, 2026):

Addressed!

<!-- gh-comment-id:4104668406 --> @tjbck commented on GitHub (Mar 21, 2026): Addressed!
GiteaMirror commented 2026-04-25 09:34:17 -05:00
Author
Owner
Copy Link

@silentoplayz commented on GitHub (Mar 22, 2026):

Addressed!

LGTM, thanks!

<!-- gh-comment-id:4105743466 --> @silentoplayz commented on GitHub (Mar 22, 2026): > Addressed! LGTM, thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug confirmed issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#35346
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?