mirror of
https://github.com/ionic-team/ionic-framework.git
synced 2025-11-07 23:16:52 +08:00
Update README.md
This commit is contained in:
11
README.md
11
README.md
@ -12,16 +12,15 @@ Framework!
|
|||||||
|
|
||||||
Page events happen in the order shown and described below:
|
Page events happen in the order shown and described below:
|
||||||
|
|
||||||
1. __pageinit__: The user clicked an internal webapp link, which triggers this event before the next page to show is either requested from the server or retrieved from the cache.
|
1. __pageinit__: The user clicked an internal webapp link, which triggers this event before the next page is either requested from the server or retrieved from the cache.
|
||||||
- __pageinitfailed__: This event is triggered when something has gone wrong while trying to receive data for the next page to show.
|
- __pageinitfailed__: This event is triggered when something has gone wrong while trying to receive data for the next page to show.
|
||||||
2. __pageafteradd__: This event is trigger after the new page has been added to the DOM. However, the new page has not started the transition to be in view yet, and the old page is still in view for the user.
|
2. __pagecreate__: This event is trigger after the new page has been added to the DOM. However, the new page has not started the transition to be in view yet, and the old page is still in view for the user.
|
||||||
3. __pageload__: The new page to show the user has already been received from the server or cache, and has been placed into the DOM. However, it has not started or ended the page transition, it is not being shown to the user, and the old page it's replacing is still being shown to the user.
|
3. __pageload__: The new page the user will view has already been received from the server or cache, and has been placed into the DOM. However, it has not started or ended the page transition, it is not in view for the user, and the old page it's replacing is still in view.
|
||||||
4. __pageshow__: The new page to show the user has already been received from the server or cache, it has been placed into the DOM, the page transition has completed. This is primarily the event you'll want to listen to to know when a new page is being shown. Note that while the the old page is not showing, the old page has not been removed from the DOM yet.
|
4. __pageview__: The new page the user is viewing has already been received from the server or cache, it has been placed into the DOM, the page transition has completed. This is primarily the event you'll want to listen to to know when a new page is being viewed. Note that while the the old page is not showing, the old page has not been removed from the DOM yet.
|
||||||
5. __pagebeforeremove__: The new page is already being shown to the user and the old page has transitioned out of view. This event is trigger before the old page is about to be removed from the DOM.
|
5. __pageremove__: The new page is already being viewed by the user and the old page has transitioned out of view. This event is triggered before the old page is about to be removed from the DOM.
|
||||||
|
|
||||||
|
|
||||||
### WebApp Events
|
### WebApp Events
|
||||||
|
|
||||||
__ready__: The DOM is ready.
|
__ready__: The DOM is ready.
|
||||||
|
|
||||||
__initalized__: The start page of the webapp has been initalized.
|
|
||||||
|
|||||||
Reference in New Issue
Block a user