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

[GH-ISSUE #17141] issue: Cmd+Enter shortcut to send message fails after activating IME #56848

New Issue
Closed
opened 2026-05-05 20:09:54 -05:00 by GiteaMirror · 3 comments
GiteaMirror commented 2026-05-05 20:09:54 -05:00
Owner
Copy Link

Originally created by @detecti1 on GitHub (Sep 2, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/17141

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Docker

Open WebUI Version

v0.6.26

Ollama Version (if applicable)

No response

Operating System

macOS 15.6

Browser (if applicable)

Chrome 138

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 Enter Key Behavior set to Ctrl+Enter to Send, pressing Cmd+Enter (or Ctrl+Enter) should send the message.

Actual Behavior

After upgrading from v0.6.21 to v0.6.26, the Cmd+Enter shortcut to send a message stops working if an Input Method Editor (IME) has been activated at any point during the session.

Once an IME (e.g., for Chinese, Japanese, or Korean input) is used in the message field, the shortcut becomes permanently disabled for that page load. This happens even if the user switches back to a standard English layout and the IME is no longer active.

The shortcut only functions correctly if the user only uses a non-IME keyboard layout.

Steps to Reproduce

  1. Navigate to the message input area on a fresh page load (using version v0.6.26).
  2. Switch your system's input method to an IME (e.g., Pinyin, Hiragana).
  3. Type a few characters. You can either complete the composition or delete the characters.
  4. (Optional)Switch the input method back to a standard English layout.
  5. Press Cmd+Enter (or Ctrl+Enter). (Nothing happens)

Logs & Screenshots

N/A

Additional Information

This appears to be a regression potentially introduced by the fix for issue #16615.

I did some initial debugging to isolate the cause. My investigation led me to the new inOrNearComposition logic within MessageInput.svelte. To test whether this new logic was related to the issue, I used my browser's developer tools to override the compiled JavaScript and force the inOrNearComposition check to always return false, effectively disabling its event-blocking behavior.

After applying this change, the Cmd+Enter shortcut began working correctly under all conditions, regardless of IME usage.

While this is not a proper fix, this test strongly suggests that the new composition-handling logic is incorrectly preventing the keydown event for the shortcut from propagating, even after the IME is no longer in an active composition state.

Originally created by @detecti1 on GitHub (Sep 2, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/17141 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Docker ### Open WebUI Version v0.6.26 ### Ollama Version (if applicable) _No response_ ### Operating System macOS 15.6 ### Browser (if applicable) Chrome 138 ### 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 `Enter Key Behavior` set to `Ctrl+Enter to Send`, pressing Cmd+Enter (or Ctrl+Enter) should send the message. ### Actual Behavior After upgrading from v0.6.21 to v0.6.26, the Cmd+Enter shortcut to send a message stops working if an Input Method Editor (IME) has been activated at any point during the session. Once an IME (e.g., for Chinese, Japanese, or Korean input) is used in the message field, the shortcut becomes permanently disabled for that page load. This happens even if the user switches back to a standard English layout and the IME is no longer active. The shortcut only functions correctly if the user only uses a non-IME keyboard layout. ### Steps to Reproduce 1. Navigate to the message input area on a fresh page load (using version v0.6.26). 2. Switch your system's input method to an IME (e.g., Pinyin, Hiragana). 3. Type a few characters. You can either complete the composition or delete the characters. 4. (Optional)Switch the input method back to a standard English layout. 5. Press Cmd+Enter (or Ctrl+Enter). (Nothing happens) ### Logs & Screenshots N/A ### Additional Information This appears to be a regression potentially introduced by the fix for issue #16615. I did some initial debugging to isolate the cause. My investigation led me to the new `inOrNearComposition` logic within `MessageInput.svelte`. To test whether this new logic was related to the issue, I used my browser's developer tools to override the compiled JavaScript and force the `inOrNearComposition` check to always return `false`, effectively disabling its event-blocking behavior. After applying this change, the `Cmd+Enter` shortcut began working correctly under all conditions, regardless of IME usage. While this is not a proper fix, this test strongly suggests that the new composition-handling logic is incorrectly preventing the keydown event for the shortcut from propagating, even after the IME is no longer in an active composition state.
GiteaMirror added the bug label 2026-05-05 20:09:54 -05:00
GiteaMirror commented 2026-05-05 20:10:00 -05:00
Author
Owner
Copy Link

@GrayXu commented on GitHub (Sep 3, 2025):

Same problem, no matter what sending method is set, as long as the input method is opened, the hotkeys will become invalid.

<!-- gh-comment-id:3249136662 --> @GrayXu commented on GitHub (Sep 3, 2025): Same problem, no matter what sending method is set, as long as the input method is opened, the hotkeys will become invalid.
GiteaMirror commented 2026-05-05 20:10:01 -05:00
Author
Owner
Copy Link

@FZZoooh commented on GitHub (Sep 6, 2025):

Same problem on Windows. Whatever the sending key is set to, Enter or Ctrl + Enter, it fails. Once the IME has been used (even if it is disabled later again), Enter always inserts a new line, instead of sending the message.
I upgraded it from 0.6.22 to 0.6.26 and then found this problem.

<!-- gh-comment-id:3262161377 --> @FZZoooh commented on GitHub (Sep 6, 2025): Same problem on Windows. Whatever the sending key is set to, Enter or Ctrl + Enter, it fails. Once the IME has been used (even if it is disabled later again), Enter always inserts a new line, instead of sending the message. I upgraded it from 0.6.22 to 0.6.26 and then found this problem.
GiteaMirror commented 2026-05-05 20:10:02 -05:00
Author
Owner
Copy Link

@CodeBoy2006 commented on GitHub (Sep 10, 2025):

It seems to have been fixed in version 0.6.27

<!-- gh-comment-id:3274870829 --> @CodeBoy2006 commented on GitHub (Sep 10, 2025): It seems to have been fixed in version 0.6.27
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
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#56848
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?