New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 752519 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Feature


Show other hotlists

Hotlists containing this issue:
interesting-issues


Sign in to add a comment

Feature Request: API support for entering and exiting kiosk mode

Reported by mike.pow...@learninglogistics.com, Aug 4 2017

Issue description

Version: Future
OS: Chrome OS

There are times when an application needs to be able to control when it enters and exits kiosk mode. 

In education, an online testing app only needs to be in kiosk mode when sensitive test content is being displayed. It is often cumbersome to be in kiosk mode when a student is just signing in and getting ready to take a test. 

In health care, there could be cases where an app is used by both patients and staff. The app would need to be able to programmatically toggle between modes depending on which user is on the device to protect sensitive data. 




 
Cc: sduraisamy@chromium.org
Labels: -Type-Bug Type-Feature
Status: Available (was: Unconfirmed)
Please see here - https://developer.chrome.com/apps/app_runtime#event-onLaunched

There is an optional parameter called isKioskSession. You can use that parameter to determine if an App is running in Kiosk mode.
This feature request is not about determining if a device is in already in Kiosk mode. We are looking to programmatically control the locking and unlocking of a device while our application is running. 

Comment 4 by mbre...@gmail.com, Oct 8 2017

It sounds like this could be addressed via https://bugs.chromium.org/p/chromium/issues/detail?id=729340
Project Member

Comment 5 by sheriffbot@chromium.org, Oct 9

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment