When my soft keyboard disappears and web content scrolls sideways, the content is rendered blank even though it is supposed to be on screen.
Reported by
damon.de...@gmail.com,
Apr 14 2016
|
|||
Issue descriptionExample URL: load the attached standalone html file in android chrome Steps to reproduce the problem: 1. Load up the attached file in android chrome 2. click into the input to raise android keyboard 3. click "next layout" on screen What is the expected behavior? you should see a heading and a list of three items What went wrong? the page goes blank, if I inspect it with remote debugger I can see the elements there, and if I toggle the display state of any elements then it reappears, but just the combination of closing the keyboard at the same time as scrolling across makes the screen go blank. Does it occur on multiple sites: No Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 49.0.2623.108 Channel: stable OS Version: 49.0.2623.105 Flash Version: Happens 100% of the time on my Samsung Galaxy S6 If you press the keyboard "go" button then it works fine, and if you press the next button without the keyboard it also works, it seems to just be caused by the keyboard going down at the same time as the screen scrolling across. I cut this one down to the minimal test page, if you modify some things, like making the viewport bottom:0 or take out the header paddings then it doesn't happen. I've gone to some effort to make narrow this one down so please let me know if there's anything else I can do to help debug.
,
Apr 17 2017
This issue has been available for more than 365 days, and should be re-evaluated. Please re-triage this issue. The Hotlist-Recharge-Cold label is applied for tracking purposes, and should not be removed after re-triaging the issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 17 2017
The bug report doesn't explain why this should be considered a Chrome bug as opposed to an HTML bug, so archiving this. |
|||
►
Sign in to add a comment |
|||
Comment 1 by ppolise...@chromium.org
, Apr 14 2016Status: Available (was: Unconfirmed)