mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 10:58:17 -05:00
[GH-ISSUE #23019] issue: Prefilled input value resets when sending "input" event call #58535
Reference in New Issue
Block a user
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 @souhailsadat on GitHub (Mar 25, 2026).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/23019
Check Existing Issues
Installation Method
Other
Open WebUI Version
v0.8.10
Ollama Version (if applicable)
No response
Operating System
Ubuntu 24.04 (Git Clone), Windows 11 (Docker)
Browser (if applicable)
Chrome, Firefox
Confirmation
README.md.Expected Behavior
When sending an event call of type
inputwith a prefilledvalue, the prefilled value should be correctly sent to the user.Actual Behavior
In most cases (but not always), the prefilled
valueis reset and sent empty to the user.Steps to Reproduce
Logs & Screenshots
Filter function implementation (sending input event with prefilled value):
First trigger: input dialog with correctly prefilled value:
Subsequent trigger: input dialog with empty value (unexpected behavior):
Additional Information
Problematic Code
The issue appears to be caused by the changes introduced in commit fb26be7.
The goal of this commit was to reset the confirm dialog input when showing it, in order to avoid accidentally sending a previous user value. However, this behavior has an unintended side effect: it resets the value every time, even when the input is intentionally prefilled during an
inputevent call.Proposed Solution
Introduce a boolean variable in
src/lib/components/chat/Chat.svelteto indicate whether the value is prefilled, and bind it toConfirmDialog.svelte.Then, in
src/lib/components/common/ConfirmDialog.svelte, reset the input value only if the boolean is false:I can submit a pull request implementing this fix if needed.
@silentoplayz commented on GitHub (Mar 25, 2026):
I can confirm that I am able to reproduce this issue on the latest
devcommit.