[Bug 59540] New: Wine's ImmNotifyIME implementation does not generate WM_IME_ENDCOMPOSITION when called with NI_COMPOSITIONSTR

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59540

            Bug ID: 59540
           Summary: Wine's ImmNotifyIME implementation does not generate
                    WM_IME_ENDCOMPOSITION when called with
                    NI_COMPOSITIONSTR
           Product: Wine
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: minor
          Priority: P2
         Component: imm32
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 80581
  --> http://bugs.winehq.org/attachment.cgi?id=80581
Bug Report - and hotfix to resolve issue with steam / proton

Summary

Wine's ImmNotifyIME implementation does not generate WM_IME_ENDCOMPOSITION
when called with NI_COMPOSITIONSTR / CPS_COMPLETE. On Windows, this call
completes the active composition and posts WM_IME_ENDCOMPOSITION to the
associated window. On Wine, the underlying NotifyIME is a stub that returns
FALSE and no composition window messages are ever posted.

Any application that uses IME composition lifecycle messages
(WM_IME_STARTCOMPOSITION / WM_IME_ENDCOMPOSITION) to track whether it is in
text-input mode will get permanently stuck after the first text entry session,
because Wine never signals the end of composition.

Affected component

Wine dlls/imm32 — specifically the default IME driver's NotifyIME and
ImeSetActiveContext stubs, and the lack of WM_IME_COMPOSITION /
WM_IME_ENDCOMPOSITION message generation in the composition lifecycle.

This is an upstream Wine bug. Proton inherits it.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.

[Bug 59540] Wine's ImmNotifyIME implementation does not generate WM_IME_ENDCOMPOSITION when called with NI_COMPOSITIONSTR

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=59540

--- Comment #1 from daniel <[e-mail]> ---
disclaimer: yes - I used AI tools to generate this. The submission of this bug
report was a human one though. The content is AI. I hope it helps.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.