fix: don't destroy BrowserView webContents on owner window close #42136
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
Closes #42033.
Refs #35658
The above PR made it such that we explicitly destroyed the webContents in all BrowserViews currently attached to a give BrowserWindow when the BrowserWindow closed, which was a breaking change from previous BrowserView behavior. We should preserve the previous behavior.
cc @nornagon in case this was for a specific reason i'm not aware of!
Checklist
npm test
passesRelease Notes
Notes: Fixed an issue where
BrowserView
webContents
were destroyed on ownerBrowserWindow
closure.