fix: set default menu in will-finish-launching event #23214
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of Change
Close #23026, which was regressed due to
setDefaultApplicationMenu
being changed to usewhenReady
. When user usesready
event directly, their callback would be called beforesetDefaultApplicationMenu()
and the default menu would override their menu settings.It is hard to ensure the
setDefaultApplicationMenu
is called before user'sready
callbacks, especially when promises are involved. However we can use thewill-finish-launching
event which is guaranteed to be called before theready
event, and we have explicitly documented that users should only create window after theready
event.Checklist
npm test
passesRelease Notes
Notes: Fix
win.setMenuBarVisibility(false)
not hiding menu bar.