electron: [Bug]: Electron ignores XCompose settings when running natively on Wayland

Preflight Checklist

• I have read the Contributing Guidelines for this project.
• I agree to follow the Code of Conduct that this project adheres to.
• I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Electron Version

12.0.7

What operating system are you using?

Other Linux

Operating System Version

Arch Linux

What arch are you using?

x64

Last Known Working Electron version

No response

Expected Behavior

1. Start a Sway session.

2. Run swaymsg 'input * xkb_options "compose:menu"' to enable XCompose on the Menu key. (See man 7 xkeyboard-config | grep 'compose:' for keys other than Menu that you can use.)

3. Put

   --enable-features=UseOzonePlatform
   --ozone-platform=wayland
   

   into your ~/.config/electron-flags.conf.

4. Run the Hash sample Electron app. I.e. do

   git clone https://github.com/electron/simple-samples .
   cd hash
   npm start
   

5. Focus on the first input field in the Hash app window.

6. Input symbols using XCompose:

   1. Press the following in sequence: Menu - - -. It must produce the em-dash symbol in the input field, “—”.

   2. Press the following in sequence: Menu = >. It must produce the double arrow symbol, “⇒”.

Actual Behavior

The last step does not produce any of the expected symbols in the input field. Instead of em-dash it produces three sort minus signs “---”, and instead of double arrow it produces “=>”.

Testcase Gist URL

No response

Additional Information

Everything works as expected and XCompose produces “—” and “⇒” if I omit the step 3, i.e. run Electron without the --enable-features=UseOzonePlatform --ozone-platform=wayland options.