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

Issue 766830 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug


Participants' hotlists:
Fixing-touch


Sign in to add a comment

Can't Disable VirtualKeyboard

Reported by jos...@gojisystems.com, Sep 19 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.79 Safari/537.36

Steps to reproduce the problem:
1. We have a kiosk application that we've built on ChromeOS.  Out Kiosk application has an angular2 keyboard we designed
2. When we go to type on a field, the chromeOS virtual keyboard keeps popping up on top of the screen so we can't use our custom angular2 keyboard
3.

What is the expected behavior?
The expected behavior is that the ChromeOS keyboard doesn't pop up and is permanently disabled.

What went wrong?
We followed the following documentation.
https://developer.chrome.com/apps/accessibilityFeatures

and it doesn't seem to be working for us.

Did this work before? No 

Does this work in other browsers? N/A

Chrome version: 61.0.3163.79  Channel: stable
OS Version: 60.0.3112.114
Flash Version: 

Since its not working, we not sure if we're doing something wrong on our end. 

Please advise.  Thank you.
 
Components: UI>Input>VirtualKeyboard
Owner: blakeo@chromium.org
Status: Assigned (was: Unconfirmed)
Blake, this issue looks like one of your assigned issues. Can you mark as Duplicate if so?

Comment 5 by blakeo@chromium.org, Feb 27 2018

Owner: oka@chromium.org
This is different. This is disabling the keyboard from the kiosk side, not the developer side (which can be different i.e. 3rd party controls or frameworks where adding inputmode=none is not straightforward). 

Because this is inherent to their kiosk experience, I think this is a good fit for the restrict features API. Moving to oka@

Comment 6 by shend@chromium.org, Jun 29 2018

Owner: ----
Status: Available (was: Assigned)
Bulk edit: oka@ is no longer working on virtual keyboard.
Owner: pcovell@chromium.org
Status: Assigned (was: Available)
Hi pcovell@, is this something we should add to the restrict features API?

Sign in to add a comment