Enable text-input-v1 support for Wayland IME under KWin/Weston/Hyprland #350
Conversation
This file contains 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
|
Started test build 28399 |
|
Build 28399 successful |
|
@q234rty can you verify that the build from @flathubbot works? Then we can go ahead with this PR (I'll also validate this tonight. |
|
@SISheogorath I tried the build and can confirm that IME works for me. |
|
Thanks! |
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.
Chromium supports text-input-v1 under ozone wayland but requires the flag
--enable-wayland-imeto enable it. KWin added support for this in https://invent.kde.org/plasma/kwin/-/merge_requests/3403 and Hyprland just landed support for this in hyprwm/Hyprland#1778 as well.