ModifiersChanged not working on WASM

[boondocklabs]

Is your issue REALLY a bug?

• My issue is indeed a bug!
• I am not crazy! I will not fill out this form just to ask a question or request a feature. Pinky promise.

Is there an existing issue for this?

• I have searched the existing issues.

Is this issue related to iced?

• My hardware is compatible and my graphics drivers are up-to-date.

What happened?

Using a text_editor on wasm, using a modifier + key just results in a regular keypress instead of a modified key. (Ctrl-C just types the letter c)

What is the expected behavior?

Modifiers are applied to keystrokes

Version

master

Operating System

macOS

Do you have any log output?

No response

[boondocklabs]

I've debugged this down to winit only producing ModifiersChanged events onto WindowId 1 which is the window created for the compositor created during boot. which is not inserted into the window manager.

When events arrive for this WindowId, they are dropped . Other events seem to be duplicated between both WindowId's, but ModifiersChanged is not, so the window attached to the canvas doesn't receive the event.

I'm wondering if it would be best to have a single window created per canvas on wasm targets, both to squelch duplicate events (they're dropped, but still adding overhead), and to fix the missing event propagation.