[PR #13068] [CLOSED] fix: Optimize sidebar chat hover behavior #38716

New Issue

GiteaMirror · 2026-04-25T11:36:01-05:00

GiteaMirror commented

2026-04-25 11:36:01 -05:00

📋 Pull Request Information

Original PR: https://github.com/open-webui/open-webui/pull/13068
Author: @cr-zhichen
Created: 4/20/2025
Status: ❌ Closed

Base: dev ← Head: dev

📝 Commits (2)

a7e12d9 fix: fix excessive bandwidth usage caused by loading full chat content on hover in Sidebar
d2de674 fix(sidebar): ensure only one chat is selected at a time, including inside folders

📊 Changes

4 files changed (+56 additions, -23 deletions)

View changed files

📝 src/lib/components/layout/Sidebar.svelte (+20 -4)
📝 src/lib/components/layout/Sidebar/ChatItem.svelte (+9 -19)
📝 src/lib/components/layout/Sidebar/Folders.svelte (+9 -0)
📝 src/lib/components/layout/Sidebar/RecursiveFolder.svelte (+18 -0)

📄 Description

Pull Request Checklist

Note to first-time contributors: Please open a discussion post in Discussions and describe your changes before submitting a pull request.

https://github.com/open-webui/open-webui/discussions/13067

Before submitting, make sure you've checked the following:

Target branch: Please verify that the pull request targets the dev branch.
Description: Provide a concise description of the changes made in this pull request.
Changelog: Ensure a changelog entry following the format of Keep a Changelog is added at the bottom of the PR description.
Documentation: Have you updated relevant documentation Open WebUI Docs, or other documentation sources?
Dependencies: Are there any new dependencies? Have you updated the dependency versions in the documentation?
Testing: Have you written and run sufficient tests to validate the changes?
Code review: Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
Prefix: To clearly categorize this pull request, prefix the pull request title using one of the following:
- BREAKING CHANGE: Significant changes that may affect compatibility
- build: Changes that affect the build system or external dependencies
- ci: Changes to our continuous integration processes or workflows
- chore: Refactor, cleanup, or other non-functional code changes
- docs: Documentation update or addition
- feat: Introduces a new feature or enhancement to the codebase
- fix: Bug fix or error correction
- i18n: Internationalization or localization changes
- perf: Performance improvement
- refactor: Code restructuring for better maintainability, readability, or scalability
- style: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
- test: Adding missing tests or correcting existing tests
- WIP: Work in progress, a temporary label for incomplete or ongoing work

Changelog Entry

Description

Optimized the hover behavior of sidebar chat items to avoid unnecessary data requests, improving overall performance and bandwidth utilization. Simplified state management, especially beneficial for chats with numerous images, while maintaining existing drag-and-drop functionality.

Added

[List any new features, functionalities, or additions - None mentioned]

Changed

When dragging a chat item from the sidebar, only chat metadata (id, title) is passed, no longer the full chat object containing all messages.

Deprecated

[List any deprecated functionality or features that have been removed - None mentioned]

Removed

Removed the logic for automatically requesting full chat content (including all messages and base64 images) when the mouse hovers over a chat item in the sidebar.

Fixed

Fixed the issue where hovering over sidebar chat items repeatedly requested the full chat content, causing significant unnecessary data transfer, bandwidth waste, and performance degradation, especially for chats with many images.

Security

[List any new or updated security-related changes, including vulnerability fixes - None mentioned]

Breaking Changes

BREAKING CHANGE: [List any breaking changes affecting compatibility or functionality - None mentioned]

Additional Information

Problem Fix:
Previously, hovering the mouse over a chat item in the sidebar would automatically request and load the entire content of that chat (including all messages and base64 images). If a chat contained a large number of images, this would result in a significant amount of data being repeatedly transferred each time the hover occurred, greatly wasting bandwidth and impacting performance.
Impact:
Now, the full chat data is only fetched when truly needed (e.g., clicking to open the chat or initiating a drag operation), significantly improving efficiency, reducing bandwidth consumption, and enhancing the user experience, especially for users with many chats or chats containing large media files.

Screenshots or Videos

[Attach any relevant screenshots or videos demonstrating the changes - Add if available]

Contributor License Agreement

By submitting this pull request, I confirm that I have read and fully agree to the CONTRIBUTOR_LICENSE_AGREEMENT, and I am providing my contributions under its terms.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/open-webui/open-webui/pull/13068 **Author:** [@cr-zhichen](https://github.com/cr-zhichen) **Created:** 4/20/2025 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `dev` --- ### 📝 Commits (2) - [`a7e12d9`](https://github.com/open-webui/open-webui/commit/a7e12d968e7513899e10421ca5aa7f04a8831fa3) fix: fix excessive bandwidth usage caused by loading full chat content on hover in Sidebar - [`d2de674`](https://github.com/open-webui/open-webui/commit/d2de674b02b0b89ab922866b4a31f26074e877be) fix(sidebar): ensure only one chat is selected at a time, including inside folders ### 📊 Changes **4 files changed** (+56 additions, -23 deletions) <details> <summary>View changed files</summary> 📝 `src/lib/components/layout/Sidebar.svelte` (+20 -4) 📝 `src/lib/components/layout/Sidebar/ChatItem.svelte` (+9 -19) 📝 `src/lib/components/layout/Sidebar/Folders.svelte` (+9 -0) 📝 `src/lib/components/layout/Sidebar/RecursiveFolder.svelte` (+18 -0) </details> ### 📄 Description # Pull Request Checklist ### Note to first-time contributors: Please open a discussion post in [Discussions](https://github.com/open-webui/open-webui/discussions) and describe your changes before submitting a pull request. https://github.com/open-webui/open-webui/discussions/13067 **Before submitting, make sure you've checked the following:** - [x] **Target branch:** Please verify that the pull request targets the `dev` branch. - [x] **Description:** Provide a concise description of the changes made in this pull request. - [x] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description. - [ ] **Documentation:** Have you updated relevant documentation [Open WebUI Docs](https://github.com/open-webui/docs), or other documentation sources? - [ ] **Dependencies:** Are there any new dependencies? Have you updated the dependency versions in the documentation? - [ ] **Testing:** Have you written and run sufficient tests to validate the changes? - [x] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards? - [x] **Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following: - **BREAKING CHANGE**: Significant changes that may affect compatibility - **build**: Changes that affect the build system or external dependencies - **ci**: Changes to our continuous integration processes or workflows - **chore**: Refactor, cleanup, or other non-functional code changes - **docs**: Documentation update or addition - **feat**: Introduces a new feature or enhancement to the codebase - **fix**: Bug fix or error correction - **i18n**: Internationalization or localization changes - **perf**: Performance improvement - **refactor**: Code restructuring for better maintainability, readability, or scalability - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.) - **test**: Adding missing tests or correcting existing tests - **WIP**: Work in progress, a temporary label for incomplete or ongoing work # Changelog Entry ### Description - Optimized the hover behavior of sidebar chat items to avoid unnecessary data requests, improving overall performance and bandwidth utilization. Simplified state management, especially beneficial for chats with numerous images, while maintaining existing drag-and-drop functionality. ### Added - [List any new features, functionalities, or additions - *None mentioned*] ### Changed - When dragging a chat item from the sidebar, only chat metadata (id, title) is passed, no longer the full chat object containing all messages. ### Deprecated - [List any deprecated functionality or features that have been removed - *None mentioned*] ### Removed - Removed the logic for automatically requesting full chat content (including all messages and base64 images) when the mouse hovers over a chat item in the sidebar. ### Fixed - Fixed the issue where hovering over sidebar chat items repeatedly requested the full chat content, causing significant unnecessary data transfer, bandwidth waste, and performance degradation, especially for chats with many images. ### Security - [List any new or updated security-related changes, including vulnerability fixes - *None mentioned*] ### Breaking Changes - **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality - *None mentioned*] --- ### Additional Information - **Problem Fix:** Previously, hovering the mouse over a chat item in the sidebar would automatically request and load the entire content of that chat (including all messages and base64 images). If a chat contained a large number of images, this would result in a significant amount of data being repeatedly transferred each time the hover occurred, greatly wasting bandwidth and impacting performance. - **Impact:** Now, the full chat data is only fetched when truly needed (e.g., clicking to open the chat or initiating a drag operation), significantly improving efficiency, reducing bandwidth consumption, and enhancing the user experience, especially for users with many chats or chats containing large media files. ### Screenshots or Videos - [Attach any relevant screenshots or videos demonstrating the changes - *Add if available*] ### Contributor License Agreement By submitting this pull request, I confirm that I have read and fully agree to the [CONTRIBUTOR_LICENSE_AGREEMENT](CONTRIBUTOR_LICENSE_AGREEMENT), and I am providing my contributions under its terms. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

GiteaMirror added the pull-request label 2026-04-25 11:36:01 -05:00

GiteaMirror closed this issue

2026-04-25 11:36:01 -05:00

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/open-webui#38716