-
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
emscripten_request_fullscreen_strategy callback order #9097
Comments
Interesting. It may be worth looking at the fullscreen tests in the cc @juj who wrote most of that code. |
For the record no issues to report in RenPyWeb so far (besides actually fixing full-screen support ;)). |
kripken
added a commit
that referenced
this issue
Nov 1, 2019
… is before the screen has resized. Fixes #9097
Thanks, yeah, that seems right to me. I opened #9765 |
kripken
added a commit
that referenced
this issue
Nov 13, 2019
That is before the screen has actually resized. The callback will be called at the proper time later. Fixes #9097
belraquib
pushed a commit
to belraquib/emscripten
that referenced
this issue
Dec 23, 2020
…ipten-core#9765) That is before the screen has actually resized. The callback will be called at the proper time later. Fixes emscripten-core#9097
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With this test code:
Pressing F, F (using
emscripten_exit_fullscreen
) results in:And pressing F, Esc (cancelling through the browser) results in:
When using
emscripten_exit_fullscreen
, the resize callback gets called before restoring the old size. It looks like what happens is:emscripten_exit_fullscreen
calls.exitFullscreen
__currentFullscreenStrategy
fullscreenchange
handler for restoreOldStyle gets called__currentFullscreenStrategy
is 0 so the resize callback doesn't get called.Removing the
if (__currentFullscreenStrategy.canvasResizedCallback)
block inemscripten_exit_fullscreen
seems to work, but I'm not sure if that would break something else.See: emscripten-ports/SDL2#87
The text was updated successfully, but these errors were encountered: