fix(ime): the candidate window position of fcitx5 which does't work well with winit's set_ime_cursor_area() - #291
Merged
Conversation
This was referenced Mar 18, 2026
…th winit's set_ime_cursor_area()
kenz-gelsoft
force-pushed
the
fix_linux_cand_pos_pop
branch
from
March 21, 2026 23:10
e81a677 to
0abe361
Compare
wash2
approved these changes
Mar 23, 2026
This was referenced Apr 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
see iced-rs#3259 for more context.
As far as I tested, ibus + winit works well with cursor areas of the top-left position and height, the candidate window doesn't hide the composing text(a.k.a. preedit) like other platforms.
But fcitx5 + winit combination doesn't work well, it is hard to input as the candidate window hides the composing text.
For our COSMIC use-case, the behavior with fcitx5 is much more important.