Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

input method popup is not shown with text input v1 clients #2315

Open
lilydjwg opened this issue Apr 6, 2024 · 1 comment
Open

input method popup is not shown with text input v1 clients #2315

lilydjwg opened this issue Apr 6, 2024 · 1 comment
Labels
easy Issues that do not require knowledge about the whole codebase enhancement PRs-welcome Issues which are unlikely to be fixed unless someone sends a PR

Comments

@lilydjwg
Copy link
Contributor

lilydjwg commented Apr 6, 2024

Describe the bug

I can use fcitx5 to input into Chrome / Qt6 apps now, but the popup doesn't appear.

To Reproduce
Steps to reproduce the behavior:

  1. Enable plugin input-method-v1
  2. Run fcitx5
  3. Run env -u QT_IM_MODULE telegram-desktop or env -u QT_IM_MODULE wireshark or /opt/google/chrome/google-chrome --ozone-platform-hint=auto --enable-wayland-ime
  4. Activate input method and type
  5. Preedit text appears and text can be committed successfully, but no im popup is shown.

Expected behavior
The popup appears.

Wayfire version
git.

@lilydjwg lilydjwg added the bug label Apr 6, 2024
@ammen99 ammen99 added enhancement easy Issues that do not require knowledge about the whole codebase PRs-welcome Issues which are unlikely to be fixed unless someone sends a PR and removed bug labels Apr 6, 2024
@ammen99
Copy link
Member

ammen99 commented Apr 6, 2024

We will need to add more methods/signals to the input method relay interfaces class, so that the input method popup v3 class doesn't actually depend on the ti-v3 struct (it is currently needed to get the focused surface and the cursor rectangle, the same info is available in ti-v1, but we need to define a common interface).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
easy Issues that do not require knowledge about the whole codebase enhancement PRs-welcome Issues which are unlikely to be fixed unless someone sends a PR
Projects
None yet
Development

No branches or pull requests

2 participants