### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for an issue that matches the one I want to file, without success.

### Issue Details

* **Electron Version:** 5.0.7
* **Operating System:** Windows 10

### Expected Behavior
When I navigate a `BrowserView` to a page that has `beforeunload` and `unload` handlers, I expect that closing the window will cause them to fire.

### Actual Behavior
They do not fire when closing the window.

Notably, if I don't use `BrowserView` and just navigate the `BrowserWindow` to the page, those handlers will execute.

### To Reproduce

`npm start` the code below (in main.js). In the devtools that opens up, run `window.onbeforeunload = () => true;`, then close the window. In the working case, the window will not close. In the broken case that uses `BrowserView`, it will.

```
const { app, BrowserWindow, BrowserView } = require('electron')

function brokenCase() {
	const mainWindow = new BrowserWindow();
	const view = new BrowserView();
	mainWindow.setBrowserView(view);
	view.webContents.loadURL("https://google.com");
	view.webContents.openDevTools();
}

function workingCase() {
	const mainWindow = new BrowserWindow();
	mainWindow.webContents.loadURL("https://google.com");
	mainWindow.webContents.openDevTools();
}

app.on('ready', brokenCase)
```

Maybe related to [this comment](https://github.com/electron/electron/issues/19194#issuecomment-544407723)
shell/browser/api/electron_api_web_contents.cc
} else {
    settings.SetBoolKey(printing::kSettingHeaderFooterEnabled, false);
  }
   We don't want to allow the user to enable these settings
   but we need to set them or a CHECK is hit.
  settings.SetIntKey(printing::kSettingPrinterType,
                     static_cast<int>(printing::PrinterType::kLocal));
  settings.SetBoolKey(printing::kSettingShouldPrintSelectionOnly, false);
  settings.SetBoolKey(printing::kSettingRasterizePdf, false);
   Set custom page ranges to print
  std::vector<gin_helper::Dictionary> page_ranges;
  if (options.Get("pageRanges", &page_ranges)) {
    base::Value page_range_list(base::Value::Type::LIST);
    for (auto& range : page_ranges) {
      int from, to;
      if (range.Get("from", &from) && range.Get("to", &to)) {
        base::Value range(base::Value::Type::DICTIONARY);
         Chromium uses 1-based page ranges, so increment each by 1.
        range.SetIntKey(printing::kSettingPageRangeFrom, from + 1);
        range.SetIntKey(printing::kSettingPageRangeTo, to + 1);
        page_range_list.Append(std::move(range));
      } else {
        continue;
      }
    }
    if (!page_range_list.GetList().empty())
      settings.SetPath(printing::kSettingPageRange, std::move(page_range_list));
  }
   Duplex type user wants to use.
  printing::mojom::DuplexMode duplex_mode =