github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 14:39:31 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #8643] No automatic focus on text field when renaming chat #102197

New Issue
Closed
opened 2026-05-17 23:37:24 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-17 23:37:24 -05:00
Owner
Copy Link

Originally created by @thgoebel on GitHub (Jan 17, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/8643

Bug Report

Installation Method

Docker

Environment

  • Open WebUI Version: 0.5.4

  • Ollama (if applicable): 0.5.4

  • Operating System: Ubuntu 24.04

  • Browser (if applicable): Firefox 134.0.1

Confirmation:

  • I have read and followed all the instructions provided in the README.md.
  • I am on 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 the exact steps to reproduce the bug in the "Steps to Reproduce" section below.

Expected Behavior:

There is automatic focus on the chat name text field.

Optionally and additionally, the entire text in the field is pre-selected (so that you can easily delete the existing value).

Actual Behavior:

There is no automatic focus on the text field.

Description

Bug Summary:
When renaming a chat, there is no automatic focus on the text field. You have to manually click on the text field.

Reproduction Details

Steps to Reproduce:

  1. Click on the overflow menu of a chat
  2. Click on "Rename"
  3. Try to type

Logs and Screenshots

Browser Console Logs:
n/a

Docker Container Logs:
n/a

Screenshots/Screen Recordings (if applicable):
n/a

Additional Information

n/a

Notes

I find this bug template confusing. Most templates out there use the following order:

  • Description/summary
  • Steps to reproduce
  • Actual behaviour
  • Expected behaviour
  • Metadata/version info
  • Logs

This template, however, is upside down. E.g., why would you want the "Expected behaviour" to be BEFORE "Description"??

Also the two subtitles "Bug Summary:" and "Steps to Reproduce:" are duplicate/unnecessary, their respective sections already have a ##-title.

Originally created by @thgoebel on GitHub (Jan 17, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/8643 # Bug Report ## Installation Method Docker ## Environment - **Open WebUI Version:** 0.5.4 - **Ollama (if applicable):** 0.5.4 - **Operating System:** Ubuntu 24.04 - **Browser (if applicable):** Firefox 134.0.1 **Confirmation:** - [x] I have read and followed all the instructions provided in the README.md. - [x] I am on the latest version of both Open WebUI and Ollama. - [ ] I have included the browser console logs. - [ ] I have included the Docker container logs. - [x] I have provided the exact steps to reproduce the bug in the "Steps to Reproduce" section below. ## Expected Behavior: There is automatic focus on the chat name text field. Optionally and additionally, the entire text in the field is pre-selected (so that you can easily delete the existing value). ## Actual Behavior: There is no automatic focus on the text field. ## Description **Bug Summary:** When renaming a chat, there is no automatic focus on the text field. You have to manually click on the text field. ## Reproduction Details **Steps to Reproduce:** 1. Click on the overflow menu of a chat 2. Click on "Rename" 3. Try to type ## Logs and Screenshots **Browser Console Logs:** n/a **Docker Container Logs:** n/a **Screenshots/Screen Recordings (if applicable):** n/a ## Additional Information n/a ## Notes I find this bug template confusing. Most templates out there use the following order: - Description/summary - Steps to reproduce - Actual behaviour - Expected behaviour - Metadata/version info - Logs This template, however, is upside down. E.g., why would you want the "Expected behaviour" to be BEFORE "Description"?? Also the two subtitles "Bug Summary:" and "Steps to Reproduce:" are duplicate/unnecessary, their respective sections already have a `##`-title.
GiteaMirror commented 2026-05-17 23:37:25 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Jan 21, 2025):

Addressed in dev! 006208f9a9

<!-- gh-comment-id:2603788590 --> @tjbck commented on GitHub (Jan 21, 2025): Addressed in dev! 006208f9a96345120d8011628b30518287a63794
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
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#102197
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?