📝 add 'did-navigate-in-page', 'did-navigate-to-different-page', 'will-navigate' to docs

This commit is contained in:
leethomas 2016-01-01 16:05:27 -08:00
parent 911e60b507
commit 9e2b76361f
2 changed files with 36 additions and 0 deletions

View file

@ -135,8 +135,22 @@ Emitted when a user or the page wants to start navigation. It can happen when th
This event will not emit when the navigation is started programmatically with
APIs like `webContents.loadURL` and `webContents.back`.
It is also not emitted during in-page navigation, such as clicking anchor links
or updating the `window.location.hash`. Use `did-navigate-in-page` for this purpose.
Calling `event.preventDefault()` will prevent the navigation.
### Event: 'did-navigate-to-different-page'
Emitted when the new page that was navigated to is different from the previous
page.
### Event: 'did-navigate-in-page'
Emitted when the page url changes but does not cause navigation outside of the page.
Examples of this occurring are when anchor links are clicked or when the
DOM `hashchange` event is triggered.
### Event: 'crashed'
Emitted when the renderer process has crashed.