You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This code instantiates a BrowserWindow with { show: false }. Five seconds after it loads the given URL, BrowserWindow.show() is called to show the window.
Also, immediately after instantiation of the BrowserWindow, BrowserWindow.setFullScreen(true) is called.
Actual Behavior
The result is that the window is shown immediately when BrowserWindow.setFullScreen(true) is called.
I'm not sure what the expected behavior should be, because BrowserWindow.setFullScreen(true) may not make sense on a BrowserWindow that is now showing. Therefore, having BrowserWindow.setFullScreen(true) have the additional functionality to also show a BrowserWindow may be correct.
This is not reflected in the documentation, which begs the question if this functionality is intentional or accidental.
Preflight Checklist
Electron Version
30.0.4
What operating system are you using?
macOS
Operating System Version
Sonoma 14.4.1
What arch are you using?
arm64 (including Apple Silicon)
Last Known Working Electron version
No response
Expected Behavior
Consider the following code:
This code instantiates a
BrowserWindow
with{ show: false }
. Five seconds after it loads the given URL,BrowserWindow.show()
is called to show the window.Also, immediately after instantiation of the
BrowserWindow
,BrowserWindow.setFullScreen(true)
is called.Actual Behavior
The result is that the window is shown immediately when
BrowserWindow.setFullScreen(true)
is called.I'm not sure what the expected behavior should be, because
BrowserWindow.setFullScreen(true)
may not make sense on aBrowserWindow
that is now showing. Therefore, havingBrowserWindow.setFullScreen(true)
have the additional functionality to also show aBrowserWindow
may be correct.This is not reflected in the documentation, which begs the question if this functionality is intentional or accidental.
Here is a comment from an old issue touching on this functionality.
Testcase Gist URL
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: