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

Issue 660679 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Virtual keyboard does not display in a kiosk application for enrolled device

Reported by jspen...@juliusspencer.co.nz, Oct 29 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36
Platform: Platform 8530.96.0 (Official Build) stable-channel gandof

Steps to reproduce the problem:
0. Enrol Chrome OS device on Google Apps domain
1. Upload application* in developer dashboard
2. Enable flags in chrome://flags
 - Enable touch events
 - Virtual Keyboard
 - Floating virtual keyboard.
3. Select application as kiosk application in domain administration
 - (Device management > Chrome > Device Settings > Kiosk Settings)
4. Sign out of Chrome OS enrolled device
5. Select Apps from the bottom bar and select application
6. Navigate to screen with text input (EditText) and select it

* The application is packaged using ARC welder.

What is the expected behavior?
The virtual keyboard should display.

What went wrong?
The keyboard did not display.

Did this work before? N/A 

Chrome version: 53.0.2785.154 (64-bit)  Channel: stable
OS Version: 
Flash Version: 

Note that this keyboard _does_ display if the application is added as a kiosk application in developer mode on an unmanaged device and steps 5 and 6 are performed.

The workaround for now is to create your own keyboard.
 

Comment 1 by tnagel@chromium.org, Oct 30 2016

Labels: Enterprise-Triaged
Owner: pelets...@chromium.org
Assigning to Sasha who's working on kiosk.
Cc: pelets...@chromium.org
Owner: poromov@chromium.org
It is Sergey, who is workng on kiosk now.
Cc: harpreet@chromium.org mlight@chromium.org
@mlight, could you try to reproduce this as well. And update the status of this bug.


Cc: poromov@chromium.org
Owner: mlight@chromium.org
Status: Assigned (was: Unconfirmed)
Assigning this to mlight@ to try repro.

mlight@ - if you are able to repro, go ahead and assign it back to poromov@ for further investigation.

Comment 5 by mlight@chromium.org, Dec 20 2016

Changing the chrome://flags values only seems to apply to that current user session;  They don't apply to actions that occur outside that session. (That's probably a feature since there can be multiple user sessions).

There is an "Accessibility" option on the sign-in screen for enabling the virtual keyboard, but that had no effect on an ARC kiosk app and non-ARC kiosk app.  (Maybe it should?)  I suspect that it is up to the kiosk app to specifically enable the virtual keyboard, but I couldn't find any specific documentation declaring it.

Owner: sduraisamy@chromium.org
sduraisamy@ - are chrome flags suppose to work in kiosk mode?

Comment 7 by uekawa@chromium.org, May 11 2017

Labels: ARCWelder

Sign in to add a comment