Chrome Version       : 65.0.3325.209
OS Version: 10323.67.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: N/A (Chrome OS applicable only)
    Firefox:N/A (Chrome OS applicable only)
    IE/Edge:N/A (Chrome OS applicable only)

What steps will reproduce the problem?
1. Define a chrome app with manifest property "kiosk_enabled": true
2. Request a kiosk-only API permission like chrome.audio (though the fact this is kiosk only is not on the chrome.audio description page :/)
3. Use any means possible to both successfully run this app and access the API. This includes "Load unpacked extension" and dragging and dropping a crx file onto chrome://extensions.

What is the expected result?
Locally debugging an unreleased chrome kiosk app is possible.

What happens instead of that?
There does not appear to be a way to run an unpacked app in kiosk mode, leaving only the option of publishing to the Chrome Store. This is not practical for development or debugging.

Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 10323.67.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/65.0.3325.209 Safari/537.36


Any advice on the typical workflow for developing kiosk apps is appreciated, thanks!