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

Issue 762503 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Nov 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

PWA added to homescreen doesn't move input elements into view when keyboard appears

Reported by davidmax...@gmail.com, Sep 6 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36

Steps to reproduce the problem:
1. create a PWA with an input element on the lower half of the screen, and add the app to the homescreen
2. when using the browser, focus the input element - keyboard appears and input element is moved to above the keyboard
3. launch the app from the homescreen, focus the input element - keyboard appears and obscures the input element

What is the expected behavior?
I expect the input element to be moved about the keyboard in both browser and from homescreen.

What went wrong?
can't see the input element when launched from homescreen.

Did this work before? N/A 

Chrome version: 60.0.3112.113  Channel: stable
OS Version: 10.0
Flash Version: 

The app appears in the app 'drawer', which I'm lead to believe means it is installing a webapk, rather than just a regular bookmark icon.
 
Cc: krajshree@chromium.org
Components: UI>Browser>WebAppInstalls
Labels: Needs-Triage-M60 Needs-Feedback
davidmaxwaterman@ - Thanks for filing the issue...!!

Could you please provide a sample PWA to test the issue from TE-end.
This will help us in triaging the issue further.

Thanks...!!
For the record, my attempts at reproducing this with a simple PWA have so far failed - ie it does move the input field when I make a small test case based on the Polymer Starter Kit.
However, it still doesn't work for my actual app, so I need to approach it from a different angle - ie by reducing my app into a simple test case (rather than building one up from scratch).
It is tempting to think that not being able to reproduce it in a simple case implies there's not a problem; but IMO the behaviour should be the same both in-browser and when launched from home screen, so I still think it is worth pursuing. Unfortunately, this will have to wait for a while due to other project commitments (this issue is a small problem, at least at the moment).
I'll get back to you.
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 12 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
davidmaxwaterman@ As per comment #2 could you please help us with the sample test case for this issue.
Status: WontFix (was: Unconfirmed)
Due to lack of user feedback closing this issue.
Please feel free to raise a new issue if you face any chrome issue further.
Thanks..!
Yeah, sorry, but I never got round to trying it again.

Sign in to add a comment