Format the docs according to style guide

This commit is contained in:
Cheng Zhao 2016-10-04 14:41:37 +09:00
parent 3af686daff
commit c4576463e2
2 changed files with 7 additions and 4 deletions

View file

@ -26,9 +26,11 @@ The `features` string follows the format of standard browser, but each feature
has to be a field of `BrowserWindow`'s options.
**Notes:**
* Node integration will always be disabled in the opened `window` if it
is disabled on the parent window.
* Non-standard features (that are not handled by Chromium or Electron such `this-is-not-a-standard-feature`) given in features will be passed to any registered `webContent`'s `new-window` event handler in the `additional_features` argument.
* Node integration will always be disabled in the opened `window` if it is
disabled on the parent window.
* Non-standard features (that are not handled by Chromium or Electron) given in
`features` will be passed to any registered `webContent`'s `new-window` event
handler in the `additionalFeatures` argument.
### `window.opener.postMessage(message, targetOrigin)`