The implementation of the text-input-unstable-v3 protocol sends all the input to a non-enabled instance of zwp_text_input_v3. #12105
Unanswered
OnePatchGuy
asked this question in
Bugs - Input
Replies: 2 comments 8 replies
-
|
patch.txt |
Beta Was this translation helpful? Give feedback.
8 replies
-
|
@vaxerski, hi! I unfortunately don't have a Hyprland at hands, hope someone else will check (maybe the affected user by themselves?) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hyprland version
Regression
I don't know, most likely no.
Describe the bug
Hello! I'm mostly forwarding a user issue with the text-input-unstable-v3 protocol here (from there: https://youtrack.jetbrains.com/issue/JBR-5672/Wayland-support-input-methods-text-input-unstable-v3#focus=Comments-27-12856093.0-0). As you can see from idea_wayland-debug-logs.txt, Hyprland sends all text events to
zwp_text_input_v3#12, although it was never enabled.Reproduction steps
-Dawt.toolkit.name=WLToolkit.Note: you can also launch IDEA from the command line like this to observe what's happening with the protocol:
WAYLAND_DEBUG=1 idea 2>&1 | grep -E 'zwp_text_input'System info and config
Beta Was this translation helpful? Give feedback.
All reactions