Description:
Feature request to request removal of input triggers for the current Remote Screen Capture functionality on Enterprise-enrolled (managed) Chrome OS devices in Kiosk Mode.

Use case:
Many customers requesting ability to perform remote screen capturing for interactive kiosks / digital signage use cases.

Motivation:
To provide Enterprise level capabilities for customers who wish to remotely capture screen without current input trigger limitations.

Existing workarounds:
Do Not Input Trigger.  Most often achieved by NOT connecting a keyboard/mouse or any input hardware after boot/reboot.

----------

For additional details on current Remote Capture, see here:  https://support.google.com/chrome/a/answer/6179663?hl=en

Screen Capture	
Clicking Capture takes a screenshot of the device's screen and stores it in Screen Captures.

The most recent screen captures of Chrome devices are listed in reverse chronological order. Click a blue link to view the screen capture.

If a screen capture fails, you’ll see a message with one of the following error codes:

0—Generic failure.
1—Screen capture failed because user input was detected.
2—Failed to get screenshots. For example, there is no screen connected to the device.
3, 4—Failed due to server error.
5—Failed due to client error.
6—Failed because the upload url is invalid.

Note: Devices that are in kiosk mode but have had user input (for example, mouse or keyboard movements within a kiosk session) are not eligible for screenshots until they are reset. If an input is detected, screenshots can't be taken until the device is restarted to reset the input trigger. The device must auto-launch into a kiosk app for screenshots to work.