Merge pull request #12847 from electron/friendly-docs
Remove judgmental docs terms
This commit is contained in:
commit
c13d1e8ae6
13 changed files with 21 additions and 24 deletions
|
@ -26,7 +26,7 @@ this event represents the `applicationWillFinishLaunching` notification of
|
|||
`NSApplication`. You would usually set up listeners for the `open-file` and
|
||||
`open-url` events here, and start the crash reporter and auto updater.
|
||||
|
||||
In most cases, you should just do everything in the `ready` event handler.
|
||||
In most cases, you should do everything in the `ready` event handler.
|
||||
|
||||
### Event: 'ready'
|
||||
|
||||
|
|
|
@ -500,7 +500,7 @@ Emitted when the window is being resized.
|
|||
|
||||
Emitted when the window is being moved to a new position.
|
||||
|
||||
__Note__: On macOS this event is just an alias of `moved`.
|
||||
__Note__: On macOS this event is an alias of `moved`.
|
||||
|
||||
#### Event: 'moved' _macOS_
|
||||
|
||||
|
@ -825,7 +825,7 @@ on the right edge and 50 pixels of controls below the player. In order to
|
|||
maintain a 16:9 aspect ratio (standard aspect ratio for HD @1920x1080) within
|
||||
the player itself we would call this function with arguments of 16/9 and
|
||||
[ 40, 50 ]. The second argument doesn't care where the extra width and height
|
||||
are within the content view--only that they exist. Just sum any extra width and
|
||||
are within the content view--only that they exist. Sum any extra width and
|
||||
height areas you have within the overall content view.
|
||||
|
||||
#### `win.previewFile(path[, displayName])` _macOS_
|
||||
|
|
|
@ -152,7 +152,7 @@ button {
|
|||
}
|
||||
```
|
||||
|
||||
If you're setting just a custom titlebar as draggable, you also need to make all
|
||||
If you're only setting a custom titlebar as draggable, you also need to make all
|
||||
buttons in titlebar non-draggable.
|
||||
|
||||
## Text selection
|
||||
|
|
|
@ -49,7 +49,7 @@ for more information on macOS' native actions.
|
|||
|
||||
Returns `Menu`
|
||||
|
||||
Generally, the `template` is just an array of `options` for constructing a
|
||||
Generally, the `template` is an array of `options` for constructing a
|
||||
[MenuItem](menu-item.md). The usage can be referenced above.
|
||||
|
||||
You can also attach other fields to the element of the `template` and they
|
||||
|
|
|
@ -858,7 +858,7 @@ Returns:
|
|||
|
||||
Fired when the guest page has sent an asynchronous message to embedder page.
|
||||
|
||||
With `sendToHost` method and `ipc-message` event you can easily communicate
|
||||
With `sendToHost` method and `ipc-message` event you can communicate
|
||||
between guest page and embedder page:
|
||||
|
||||
```javascript
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue