Electron: Inconsistent addition of --enable-wayland-ime when NIXOS_OZONE_WL is set

[34j]

Describe the bug

I found that some packages add --enable-wayland-ime when NIXOS_OZONE_WL is set, and some do not.

• 10 Packages adding --enable-wayland-ime

• 99 Packages using NIXOS_OZONE_WL

• I am using fcitx5 and KDE Plasma 6 and setting NIXOS_OZONE_WL=1

• vesktop allows Japanese input, while VS Code and Slack do not.

• If I add the --enable-wayland-ime flag and start VS Code or Slack, I can input Japanese.

• Therefore, I suggest adding this flag to all packages that use NIXOS_OZONE_WL if NIXOS_OZONE_WL is set.

Steps To Reproduce

Steps to reproduce the behavior:

1. Use Wayland and set NIXOS_OZONE_WL=1
2. Install Fcitx5 and mozc
3. Open vesktop and Slack

Expected behavior

All packages allow Japanese input

Screenshots

Additional context

• About NIXOS_OZONE_WL: Document: The behavior of NIXOS_OZONE_WL is a bit unnatural and undocumented #291051
• This issue is also related to the problem that Electron does not provide the ability to override --enable-wayland-ime by setting an environment variable. ([Feature Request]: support IME under native Wayland electron/electron#33662 (comment))
• According to Fcitx 5 wiki, it seems it is always recommended to add --enable-wayland-ime or --gtk-version=4 (which is only supported in chromium/chrome) flag when launching Electron apps. (https://fcitx-im.org/wiki/Using_Fcitx_5_on_Wayland#Chromium_.2F_Electron)
• It is possible to add flags using ~/.config/electron-flags.conf, but "do not work for packages that bundle their own build of Electron" (https://wiki.archlinux.org/title/Wayland#Configuration_file).

Metadata

Notify maintainers

@mmahut @teutat3s
@eadwu @Synthetica9 @bobby285271 @Enzime

---

Note for maintainers: Please tag this issue in your PR.

---

Add a 👍 reaction to issues you find important.