Use the chrome.app.runtime API to manage the app lifecycle. The app runtime manages app installation, controls the event page, and can shut down the app at anytime.
Use the chrome.app.runtime API to manage the app lifecycle. The app runtime manages app installation, controls the event page, and can shut down the app at anytime. * available since Chrome 36 * https://developer.chrome.com/apps/app.runtime
(tap-all-events chan)
Taps all valid non-deprecated events in chromex.app.app.runtime namespace.
Taps all valid non-deprecated events in chromex.app.app.runtime namespace.
(tap-on-embed-requested-events channel & args)
Fired when an embedding app requests to embed this app. This event is only available on dev channel with the flag --enable-app-view.
Events will be put on the |channel| with signature [::on-embed-requested [request]] where:
|request| - https://developer.chrome.com/apps/app.runtime#property-onEmbedRequested-request.
Note: |args| will be passed as additional parameters into Chrome event's .addListener call.
https://developer.chrome.com/apps/app.runtime#event-onEmbedRequested.
Fired when an embedding app requests to embed this app. This event is only available on dev channel with the flag --enable-app-view. Events will be put on the |channel| with signature [::on-embed-requested [request]] where: |request| - https://developer.chrome.com/apps/app.runtime#property-onEmbedRequested-request. Note: |args| will be passed as additional parameters into Chrome event's .addListener call. https://developer.chrome.com/apps/app.runtime#event-onEmbedRequested.
(tap-on-launched-events channel & args)
Fired when an app is launched from the launcher.
Events will be put on the |channel| with signature [::on-launched [launch-data]] where:
|launch-data| - https://developer.chrome.com/apps/app.runtime#property-onLaunched-launchData.
Note: |args| will be passed as additional parameters into Chrome event's .addListener call.
https://developer.chrome.com/apps/app.runtime#event-onLaunched.
Fired when an app is launched from the launcher. Events will be put on the |channel| with signature [::on-launched [launch-data]] where: |launch-data| - https://developer.chrome.com/apps/app.runtime#property-onLaunched-launchData. Note: |args| will be passed as additional parameters into Chrome event's .addListener call. https://developer.chrome.com/apps/app.runtime#event-onLaunched.
(tap-on-restarted-events channel & args)
Fired at Chrome startup to apps that were running when Chrome last shut down, or when apps have been requested to restart from their previous state for other reasons (e.g. when the user revokes access to an app's retained files the runtime will restart the app). In these situations if apps do not have an onRestarted handler they will be sent an onLaunched event instead.
Events will be put on the |channel| with signature [::on-restarted []].
Note: |args| will be passed as additional parameters into Chrome event's .addListener call.
https://developer.chrome.com/apps/app.runtime#event-onRestarted.
Fired at Chrome startup to apps that were running when Chrome last shut down, or when apps have been requested to restart from their previous state for other reasons (e.g. when the user revokes access to an app's retained files the runtime will restart the app). In these situations if apps do not have an onRestarted handler they will be sent an onLaunched event instead. Events will be put on the |channel| with signature [::on-restarted []]. Note: |args| will be passed as additional parameters into Chrome event's .addListener call. https://developer.chrome.com/apps/app.runtime#event-onRestarted.
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close