-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Browser shortcut keys don't work with an SDL2 Emscripten page that handles keypress events #16462
Comments
Ah, I got as far as committing emscripten-ports/SDL2@65c1316, but apparently never merged it. The only side-effect I can see there is not preventDefault-ing keys that SDL doesn't handle... which probably isn't a bad thing. May just rebase and push upstream when I get the chance. |
Did a quick check that |
Thanks! |
Presumably we still to update the SDL version used in emscripten? |
OK sorry I'm not sure of the process - maybe I wasn't supposed to close this? Is there anything else I need to do? |
Hmm, yeah need to update the tag here. Not sure what we're doing for updates outside of upstream releases now though... |
I believe we can update the "tag" in |
This fix was undone shortly after it was committed, by this commit libsdl-org/SDL@9221548 |
Hmm, not sure if that was intentional... or when I might get the chance to see if adding the |
I reported this issue here a while ago:
emscripten-ports/SDL2#128
That repository got archived but the issue still remains (Emscripten 3.1.7).
To summarize, I want my application to handle some keypresses, but I want the other keypresses that I don't handle to fall back on the regular browser behaviour (such as F11 making the window full screen, for Firefox).
There was a patch that fixed it which @Daft-Freak said he would need to test before applying.
I also noticed that the issue did not seem to be present in an older version of Emscripten, 1.39.8 (i.e. without the patch, the behaviour I wanted was already happening, as long as I created the FilterEvents function mentioned in that issue). I can't downgrade to work around it because that version has other issues, but it might be interesting that something other than that patch caused this behaviour to change.
The text was updated successfully, but these errors were encountered: