A while ago, we discovered some weird behavior with the bevy engine when compiling to wasm.

When opening the context menu in the browser, things behaved weirdly after that. I opened an issue on the bevy UI library we are using (link above). After some analysis it turned out that the mouse state got stuck since we don't receive a released event when pressing the right mouse button. This in turn blocks the user from using the wasm app at all since inputs are all screwed up.

This issue might be slightly related to #2455 and #2475 but it still seemed distinct enough to open a new issue.

I'll try to get a minimal reproducible example running in the near future which only utilizes winit.