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

Issue 799970 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jan 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug-Regression


Participants' hotlists:
Hotlist-1


Sign in to add a comment

on-screen keyboard doesn't work in kiosk mode (bug from issue 779968 continues)

Reported by bart.m...@sonoraquest.com, Jan 8 2018

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Platform: 10176.22.0 (official Build) beta-channel veuron_tiger

Steps to reproduce the problem:
1. use a device in touch screen only mode (no touchpad or a physical mouse). We have an Asus C100PA-DB02, and an Aopen Chromebase mini.
2. launch a webview kiosk app in a single app kiosk mode
2. when clicking on a text field, the virtual keyboard will open but will not type
uploaded a video of the behavior: https://photos.app.goo.gl/wCOdZjPUeTBQImr13 - actual app we are using. if we press "tab" button it will begin working
https://photos.app.goo.gl/jFXlYtTTbCm7wKcF3 - test app with html code that only contains one text field just to isolate the code
https://photos.app.goo.gl/0O8EfrvPBTGNz83s2 - video of another workaround that required using a physical mouse

What is the expected behavior?
virtual keyboard should work

What went wrong?
the keyboard doesn't type when pressing a text field

WebStore page: 

Did this work before? Yes 62.0.3202.97 (Official Build) (32-bit)

Chrome version: 64.0.3282.41  Channel: beta
OS Version: 64.0.3282.41
Flash Version: n/a

we originally experienced the issue in chrome 61 stable-channel, since than it went away in the latest version and is not present in latest v61 and v62 [62.0.3202.97 (Official Build) (32-bit)], but the issue returned to v63 [63.0.3239.116 (official Build) (32-bit)] and now beta v64 [64.0.3282.41 (Official Build) beta (32-bit)].

The workaround javascript in the  issue 779968  didn't work for me (or I don't know how to properly implement it). I added it to the top of background_main.js. I use Chrome App Builder Chrome browser Extension to generate our chrome kiosk apps: https://chrome.google.com/webstore/detail/chrome-app-builder/ighkikkfkalojiibipjigpccggljgdff - this app builder creates apps without this workaround.
 

Comment 1 by lfg@chromium.org, Jan 8 2018

Components: -Platform>Apps Platform>Apps>BrowserTag
Labels: OS-iOS
Owner: lfg@chromium.org

Comment 2 by lfg@chromium.org, Jan 8 2018

Labels: -OS-iOS

Comment 3 by lfg@chromium.org, Jan 8 2018

I think someone needs to update the kiosk app generator. To fix this, can you try adding this to the file 'js/cab.js', where you see:

    navigateTo: function(url) {
      if (!this.webview) {
        console.log('navigateTo: MISSING WEBVIEW');
        return;
      }
      this.webview.src = url;
    },

Add this line:

    navigateTo: function(url) {
      if (!this.webview) {
        console.log('navigateTo: MISSING WEBVIEW');
        return;
      }
      this.webview.src = url;
      this.webview.focus();
    },

Comment 4 by lfg@chromium.org, Jan 8 2018

Owner: markdittmer@chromium.org
Assigning to Mark to look at updating the app.

Comment 5 by lfg@chromium.org, Jan 8 2018

Status: Assigned (was: Unconfirmed)
Thanks lfg! This workaround worked for us :) Still wired that mouse clicks and touch clicks don't behave the same, but I don't have to worry about it any more. Thank you!
Status: Verified (was: Assigned)
lfg@chromium.org has confirmed that a newly committed fix works. Version 1.0.2 should appear in the Chrome Web Store with the fix within the hour.

Sign in to add a comment