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

[GH-ISSUE #22747] issue: Chat Input Selection Modal Does Not Reappear for Any Trigger (/, #, @, $) After Space and Backspace #35337

New Issue
Closed
opened 2026-04-25 09:33:54 -05:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-04-25 09:33:54 -05:00
Owner
Copy Link

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

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 typing a trigger character (like #, @, /, or $) followed by text (e.g., #test), the context selection modal appears. Pressing space legitimately dismisses the modal. However, if the user immediately presses backspace to return the cursor to directly adjacent to the trigger term (deleting the space), the selection modal should reappear to allow selecting the relevant item (folder, model, prompt, or skill), rather than the text simply remaining highlighted without the modal.

Actual Behavior

After typing a trigger term (e.g., #test or @model), the selection modal appears. Pressing space dismisses the modal. Pressing backspace to delete the space successfully turns the text back into a highlighted tag representation (blue text background), but the selection modal fails to reappear, preventing the user from easily selecting the intended item without re-typing the trigger. This occurs for all chat input triggers (# for documents/folders, @ for models, / for prompts, and $ for skills).

Steps to Reproduce

  1. Start an Open WebUI instance utilizing the v0.8.10 version on Ubuntu 24.04.4 LTS.
  2. Open any chat or start a new chat.
  3. In the chat input area, type a trigger character followed by some text, for example: #test for a folder/document, @model_name for a model, /prompt_name for a prompt, or $skill_name for a skill. Observe that the corresponding selection modal pops up.
  4. Press the Space bar on the keyboard. Observe that the modal disappears.
  5. Press the Backspace key to delete the space.
  6. Observe that the typed trigger text becomes highlighted in blue again, but the selection modal does not pop back up.

Logs & Screenshots

Step 3: Trigger character #test is typed, and the selection modal correctly appears.
Image

Step 4: Spacebar is pressed. Text color returns to plain text (not highlighted) and the selection modal disappears.
Image

Step 5: Backspace is pressed to delete the space. The #test text becomes highlighted as a tag again, but the selection modal (from Step 3) does not reappear.
Image

Clicking inside the tag: Attempting to click elsewhere within the tag (e.g., between letters) does not trigger the selection modal either, and can result in a "broken" tag state where the highlighting only covers part of the text.
Image

Additional Information

  • This behavior interrupts the flow if a space was accidentally typed, as the user must either erase the entire tag and re-type the trigger key.
  • As demonstrated in the final screenshot, clicking elsewhere or attempting to reposition the cursor within the "blue" highlighted region does not re-trigger the selection modal, and often leaves the input in an inconsistent visual state.
Originally created by @silentoplayz on GitHub (Mar 17, 2026). Original GitHub issue: https://github.com/open-webui/open-webui/issues/22747 ### 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 typing a trigger character (like `#`, `@`, `/`, or `$`) followed by text (e.g., `#test`), the context selection modal appears. Pressing space legitimately dismisses the modal. However, if the user immediately presses backspace to return the cursor to directly adjacent to the trigger term (deleting the space), the selection modal should reappear to allow selecting the relevant item (folder, model, prompt, or skill), rather than the text simply remaining highlighted without the modal. ### Actual Behavior After typing a trigger term (e.g., `#test` or `@model`), the selection modal appears. Pressing space dismisses the modal. Pressing backspace to delete the space successfully turns the text back into a highlighted tag representation (blue text background), but the selection modal fails to reappear, preventing the user from easily selecting the intended item without re-typing the trigger. This occurs for all chat input triggers (`#` for documents/folders, `@` for models, `/` for prompts, and `$` for skills). ### Steps to Reproduce 1. Start an Open WebUI instance utilizing the `v0.8.10` version on Ubuntu 24.04.4 LTS. 2. Open any chat or start a new chat. 3. In the chat input area, type a trigger character followed by some text, for example: `#test` for a folder/document, `@model_name` for a model, `/prompt_name` for a prompt, or `$skill_name` for a skill. Observe that the corresponding selection modal pops up. 4. Press the `Space` bar on the keyboard. Observe that the modal disappears. 5. Press the `Backspace` key to delete the space. 6. Observe that the typed trigger text becomes highlighted in blue again, but the selection modal does not pop back up. ### Logs & Screenshots **Step 3:** Trigger character `#test` is typed, and the selection modal correctly appears. <img width="425" height="244" alt="Image" src="https://github.com/user-attachments/assets/84e25fec-a875-4b25-b832-cec7a845e1a4" /> **Step 4:** Spacebar is pressed. Text color returns to plain text (not highlighted) and the selection modal disappears. <img width="434" height="256" alt="Image" src="https://github.com/user-attachments/assets/fc4c21d6-8cd1-4d4b-98da-87ded577a790" /> **Step 5:** Backspace is pressed to delete the space. The `#test` text becomes highlighted as a tag again, but the selection modal (from Step 3) does not reappear. <img width="434" height="256" alt="Image" src="https://github.com/user-attachments/assets/1ae24bd8-3cb2-4378-b206-af574e448508" /> **Clicking inside the tag:** Attempting to click elsewhere within the tag (e.g., between letters) does not trigger the selection modal either, and can result in a "broken" tag state where the highlighting only covers part of the text. <img width="313" height="139" alt="Image" src="https://github.com/user-attachments/assets/98bb6d91-2c82-42e8-8320-503fa6ccfd25" /> ### Additional Information - This behavior interrupts the flow if a space was accidentally typed, as the user must either erase the entire tag and re-type the trigger key. - As demonstrated in the final screenshot, clicking elsewhere or attempting to reposition the cursor within the "blue" highlighted region does not re-trigger the selection modal, and often leaves the input in an inconsistent visual state.
GiteaMirror added the bugconfirmed issue labels 2026-04-25 09:33:54 -05:00
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#35337
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?