Ability to take screenshot of device in kiosk mode |
|||||
Issue descriptionDescription: Enterprise customer is deploying a large number of kiosk mode devices running custom applications. IT admin and application developers have the need to be able to take screenshots of these devices remotely for testing, debugging, troubleshooting. This typically occurs *after* user input activity. This is currently disallowed by Chrome as a privacy concern, but it is critical to customers’ development activities. They would like to be able to take the screenshot, possibly with a warning prompt, countdown timer, or accept button on the screen to alert potential users to the possibility of a screenshot being taken. Use case: Kiosk mode devices are in remote locations, typically not accessible by IT admin staff as well as sometimes not easily accessible at all. When troubleshooting application problems, debugging applications in development there exists the need to see what is on the screen. Currently this can't happen in kiosk mode once user input is detected. Motivation: Kiosk applications have to be tested / debugged / troubleshooting. Usually this takes place *after* user input. The cases being tested usually require user input. It is impossible for Admin staff or developers to access the devices being tested. So they need to be able to remotely see the screen. Existing workarounds: None
,
Jan 21 2018
Assigning to Shubhar for triage. I remember that not allowing screenshots after any user input has been done was a privacy concern. This was implemented in bug 487261 , the code location is ScreenshotDelegate::IsScreenshotAllowed / StatusUploader::IsSessionDataUploadAllowed.
,
Jun 11 2018
,
Aug 3
This bug has an owner, thus, it's been triaged. Changing status to "assigned".
,
Aug 23
,
Jan 7
It's trivial to change this behavior (and I'd argue that we should change it, since we're now allowing chromoting into kiosk sessions) - only blocker would be to get privacy team buy-in.
,
Jan 7
That would be welcome. The customer involved is testing the chromoting feature and commented on how the kiosk screen shot feature was missing in the new console. Although remoting in does provide similar capability I think allowing the screen shot would still have value for troubleshooting / debugging issues. It would also consume fewer resources than a full remoting session - single screen capture vs. live video passing across network. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by krishna...@chromium.org
, Jan 18 2018