-
Notifications
You must be signed in to change notification settings - Fork 9
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
Add GTK4 IM modules #106
Add GTK4 IM modules #106
Conversation
Started test build 73244 |
Build 73244 successful
|
Started test build 73355 |
Build 73355 successful
|
Started test build 73398 |
Build 73398 successful
|
@tinywrkb is it done, or do you need more time? |
@TheEvilSkeleton this is still being discussed, see flathub/com.google.Chrome#107 |
No worries! I'm just going to mark it as draft so you can test it and later mark it as ready for review. |
Closing in favor of adding this to the Chromium base app. |
@tinywrkb can you send a link to the base app? I wasn't aware of one. |
Found it. Sorry for pinging you flathub/flathub#2886. |
I'm not sure if we really want to build and package GTK4, so this should be discussed further.
I opened an issue about this in the Chrome packaging repo.
Anyway, this adds the GTK4 IM modules to have Fcitx5 and IBus working with Ozone Wayland.
Updated GTK3 IM modules were also added.
Users need to start the browser with the
--gtk-version=4
flag.Note that Fcitx5 has an IBus backend, and the IBus IM module has popup working, so it's preferable to use the IBus IM module with the Fcitx5 daemon, or just use the IBus daemon.
If you want to stick with Fcitx5 daemon, then set an environment override
GTK_IM_MODULE=IBus
for Edge in order to use the IBus IM module.