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

Issue 788383 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Fullscreen causing soft keyboard to sit over the invoking input field, and window resize event failure

Reported by grimephi...@gmail.com, Nov 24 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0

Steps to reproduce the problem:
1. Browse to the provided source file with a mobile device. I have also provided a plunk here:
https://run.plnkr.co/plunks/ZNWL8aSKhNvtJMoLJcPD/
2. Touch input field in normal mode and note the input field moves up and is visible when keyboard opens, and resize event is recorded in the box.
3. Use the red button to toggle fullscreen mode. 
4. Touch input field in fullscreen mode and note input field is obscured when keyboard opens, and resize event is not recorded in the box.
5. Touch outside the input field to cancel input mode and close the keyboard.

What is the expected behavior?
Input field should jump up above the soft keyboard as it does when not in fullscreen mode, and resize events should be dispatched

What went wrong?
Input field is obscured by soft keyboard, and resize events are not dispatched

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 63.0.3239.59  Channel: beta
OS Version: 10.0
Flash Version: 

Chrome used to have a problem where the soft keyboard would appear on top of the input field that invoked it, this issue was fixed some time ago. However when in fullscreen mode the bug has reappeared, and the soft keyboard covers the input field. Also when in fullscreen mode, window.resize events are not dispatched when the soft keyboard opens and closes.
 
fullscreenissue.html
3.2 KB View Download
Cc: foolip@chromium.org
Labels: Needs-Triage-M63
Labels: Needs-Bisect
Cc: vamshi.k...@techmahindra.com
Labels: -Needs-Bisect Triaged-ET M-64
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on the reported chrome version 63.0.3239.59 and on the latest canary 64.0.3279.0 using Windows 10 surface pro. As the issue seems be from 62.0.3194.0 where the feature of chrome://flag "Direct manipulation stylus" got introduced. Hence treating it as non-regression and marking it as untriaged.

Comment 5 by e...@chromium.org, Nov 30 2017

Owner: foolip@chromium.org
Status: Assigned (was: Untriaged)

Sign in to add a comment