chore: fix spelling errors in multiple files (#34574)
* chore: fix spelling in .circleci Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in BUILD.gn Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in appveyor.yml Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in build Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in docs Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in lib Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in script Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in shell Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in spec Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com> * chore: fix spelling in spec-main Signed-off-by: Josh Soref <2119212+jsoref@users.noreply.github.com>
This commit is contained in:
parent
f418a49857
commit
ea4278754c
58 changed files with 88 additions and 88 deletions
|
@ -1381,7 +1381,7 @@ method returns false. If we fail to perform the copy, then this method will
|
|||
throw an error. The message in the error should be informative and tell
|
||||
you exactly what went wrong.
|
||||
|
||||
By default, if an app of the same name as the one being moved exists in the Applications directory and is _not_ running, the existing app will be trashed and the active app moved into its place. If it _is_ running, the pre-existing running app will assume focus and the previously active app will quit itself. This behavior can be changed by providing the optional conflict handler, where the boolean returned by the handler determines whether or not the move conflict is resolved with default behavior. i.e. returning `false` will ensure no further action is taken, returning `true` will result in the default behavior and the method continuing.
|
||||
By default, if an app of the same name as the one being moved exists in the Applications directory and is _not_ running, the existing app will be trashed and the active app moved into its place. If it _is_ running, the preexisting running app will assume focus and the previously active app will quit itself. This behavior can be changed by providing the optional conflict handler, where the boolean returned by the handler determines whether or not the move conflict is resolved with default behavior. i.e. returning `false` will ensure no further action is taken, returning `true` will result in the default behavior and the method continuing.
|
||||
|
||||
For example:
|
||||
|
||||
|
|
|
@ -713,7 +713,7 @@ To clear the handler, call `setDevicePermissionHandler(null)`.
|
|||
This handler can be used to provide default permissioning to devices without first calling for permission
|
||||
to devices (eg via `navigator.hid.requestDevice`). If this handler is not defined, the default device
|
||||
permissions as granted through device selection (eg via `navigator.hid.requestDevice`) will be used.
|
||||
Additionally, the default behavior of Electron is to store granted device permision through the lifetime
|
||||
Additionally, the default behavior of Electron is to store granted device permission through the lifetime
|
||||
of the corresponding WebContents. If longer term storage is needed, a developer can store granted device
|
||||
permissions (eg when handling the `select-hid-device` event) and then read from that storage with `setDevicePermissionHandler`.
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue