On screen keyboard breaks scrolling while using the fullscreen API
Reported by szd...@gmail.com, Mar 22 2017
Mar 22 2017,
Jun 15 2017,
Having the very same issue on a HTML command line UI type application. The input text field is always at the bottom, and vertical screen space is super valuable so fullscreen mode is essential. Unfortunately, the command line is obfuscated by the soft keyboard in fullscreen mode.
Hi, Resolving this issue is critical to my "text adventure game engine" type application working. This works fine on desktop OSs (without virtual keyboard), but on Android, it is terribly broken. Please fix this issue. I have created a very good demonstration of this issue as described below. Phone Used : Google Pixel 2 Operating System Used : Android 8.1.0; Pixel 2 Build/OPM1.171019.013 Browser Used : Chrome (Android) 63.0.3239.111 1) On an Android mobile phone (without hardware keyboard) .... 1) Navigate to http://eeyo.io/advdemo1 3) Click to start the adventure game. 4) Double clicking in the chrome window (double tap touch) will maximise the window (via an internal call to requestFullscreen() ) - because scrollable vertical space is REALLY important in text adventures. Ensure that the screen is now in fullscreen mode (NO NAV BUTTONS AT BOTTOM, no URL BAR AT TOP). 5) Now click the panel to put focus on the text input widget. 6) OBSERVE, the bottom part of the play area is now not visible. 7) Swipe up from the bottom of the screen. 8) Press Back Soft key (to exit full screen mode). Be careful not to double tap and re-enter full screen mode. 9) Click screen (single touch event). Now the software keyboard does not overwrite the bottom of the play area. The full play area is visible (but there is very little vertical space available. A resolution to this bug should allow fullscreen mode to be used without hiding content behind the keyboard. This bug has been open for 11 months now. Without a resolution to this bug, a mobile client that makes optimal use of screen space simply is not possible. Correct Behaviour (in non fullscreen mode): https://www.youtube.com/watch?v=B-k8mJ20ozY Demonstration of 704070 bug (in fullscreen mode): https://youtu.be/veE2LJgPXNI
Yeah, that seems pretty bad. I can't prioritize it in the next 2-3 weeks but I'll take a crack at it after that.
Any progress on this one? It's a very annoying one indeed.
Though I don't know what change is responsible, the repro in #4 appears to be working for me in 69.0.3475.0 (Dev channel). Could you please try dev channel on your own repro and see if that's working for you?
Sign in to add a comment