Typora doesn't detect IBUS on Wayland #6440
Description
-
Searched existing issues to avoid creating duplicates.
-
Confirmed that it can be reproduced in built-in themes without customized css.
If it only exists in 3rd party themes or css, you can still report it, but please attach the theme target or the css file. We may not "fix" it, if it is caused by 3rd party themes or css styles that we cannot support.
-
Searched http://support.typora.io/
Describe the bug
While using Typora on a Wayland-based Linux desktop environment like Niri, the ibus composer key and its inputs are not detected. You can use IBUS on Wayland to allow for combinations of keypresses to form different symbols and such. Typora simply does not detect any of these custom inputs.
This is using the Typora binary. Proper Chromium environment variables for Wayland have been set-up, and this bug is not present on Chromium or other Chromium-based apps, though I don't know if Typora uses an older version.
The recommended flags for Wayland (--enable-features=UseOzonePlatform --ozone-platform=wayland) have been tried with no results.
To Reproduce
Steps to reproduce the behavior:
- Use a wayland-based desktop environment with IBUS.
- Try using a compose key to input a character.
- The input is not detected by Typora.
Expected behavior
Typora should be able to read the Wayland environment variables and capture the input of IBUS.
Desktop (please complete the following information):
- OS: CachyOS with Niri Wayland Compositor
Typora Version
e.g: 1.12.2
Additional context
Thanks for taking the time to read this!