Currently all secondary extensions/apps declared by a kiosk app are loaded (and enabled) at the kiosk session startup.
This issue is to track the effort to allow the primary app to selectively enable secondary apps in a kiosk session. The feature requests consists of two parts:
1. Enable chrome.management API in kiosk (so the primary app can enable/disable secondary apps)
2. Amend kiosk.secondary_apps feature to declare a secondary app as disabled by default (i.e. an option to have the secondary kiosk app disabled at the kiosk session startup - the app would only be enabled if requested by the primary kiosk app)
Comment 1 by tbarzic@chromium.org
, Jan 18 2018