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

Issue 658256 link

Starred by 2 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

kiosk mode does not work when there is an extension with background page running

Reported by davisf...@gmail.com, Oct 21 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1. Run C:\Program Files (x86)\Google\Chrome\Application> chrome.exe --kiosk and see the browser launch in kiosk mode
2. Install our extension at https://chrome.google.com/webstore/detail/emaginepos-payments/bdmagcfhdkdmhbmgcpaopogicolehfmo?authuser=1 and close browser
3. Run C:\Program Files (x86)\Google\Chrome\Application> chrome.exe --kiosk and see the browser will no longer launch in kiosk mode.
4. Disable the extension and try again, see that it works.

What is the expected behavior?
The expected behavior is that Chrome will still launch in kiosk mode with the --kiosk flag.  

What went wrong?
We're a point of sale company that deploys our pos using Chrome in kiosk mode.  As part of our solution, I have built a Chrome extension that runs a background page.  Ever since we installed the extension, we can no longer launch Chrome in kiosk mode.  We have to manually put it in fullscreen mode which is problematic for us.

My suspicion is that our extension runs a background page https://developer.chrome.com/extensions/background_pages and this is somehow preventing kiosk mode from working.  Just having an extension installed and active doesn't seem to affect kiosk mode.  The only interesting thing about our extension is that it runs a background page.  We use only a handful of chrome apis to message between the extension and the webpage.  The rest is vanilla JS.  I can share the original, un-minified/uglified source with Google in private if it helps.  I don't want to paste it here.

Did this work before? N/A 

Chrome version: 53.0.2785.143  Channel: stable
OS Version: 6.1.7601 Service Pack 1 Build 7601
Flash Version: Shockwave Flash 23.0 r0

This is the full output about the OS:

C:\Program Files (x86)\Google\Chrome\Application>systeminfo | findstr /C:"OS"
OS Name:                   Microsoft Windows Embedded Standard
OS Version:                6.1.7601 Service Pack 1 Build 7601
OS Manufacturer:           Microsoft Corporation
OS Configuration:          Standalone Workstation
OS Build Type:             Multiprocessor Free
BIOS Version:              Dell Inc. 2.2.4, 9/4/2015

This is on a Dell Inspiron 20 touchscreen terminal.  We are a POS company and this is common hardware / deployment platform.  

Also note that I put down Chrome 54 in the description (just updated and tried it -- problem still exists), but it has been a problem for Chrome 53.x as well.
 

Comment 1 by davisf...@gmail.com, Oct 21 2016

Sorry, I meant to put Chrome 54.0.2840.71 m as the version in the description.  Please note that I updated Chrome this morning to that version and tested and the problem still persists.  It has always been a problem in all 53.x versions I have tried since I discovered the problem.

Comment 2 by e...@chromium.org, Oct 21 2016

Components: -Blink UI>Shell>Kiosk

Comment 3 by e...@chromium.org, Oct 21 2016

Components: Platform>Apps>BackgroundPage

Comment 4 by e...@chromium.org, Oct 21 2016

Labels: -Type-Bug Type-Bug-Regression
Labels: M-54 Needs-Bisect

Comment 6 by hdodda@chromium.org, Oct 24 2016

Cc: hdodda@chromium.org
Labels: -M-54 -Needs-Bisect M-56 OS-Linux
Status: Untriaged (was: Unconfirmed)
Tested on windows 7 using chrome stable M54 # 54.0.2840.71 and issue is reproduced.

Till M31 , extension cannot be added to chrome . From M32 , issue exists. Hence it is a non-regression issue.
 
Changing the milestone to M56 and removing needs-bisect label.

Note : Issue is not seen in Mac OS and issue is seen in Linux .

Thanks !

Comment 7 by davisf...@gmail.com, Nov 16 2016

Hi, some more info on this.  I am the original bug reporter, but I have not verified this myself.  This is some anecdotal info I got from one of our customers in the field, and I trust his information.

We deploy our point of sale on touchscreen hardware (e.g. Dell Inspiron 20 touchscreen terminal).  These are 64-bit machines, but we had been deploying the 32-bit version of Chrome with Windows Embedded POSReady7 https://www.microsoft.com/windowsembedded/en-us/windows-embedded-posready-7.aspx

He discovered that running the 64-bit version of Chrome on these touch-screens makes the problem go away.  Furthermore, we also make use of the flag --disable-pinch and that likewise would not work with the extension installed, but it *does* with the 64-bit version installed.

So, I'm guessing that probably provides a significant clue...hope so, anyway.

Sign in to add a comment