![Firefox for Android logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2020-04-14-08-37-28-a0d9f0_1.png)
Keyboard doesn't disappear after entering URL: Firefox Nightly for Android
In the Nov 20th and Nov 21st Nightly builds, when I enter a URL in the address bar (either by fully typing it and tapping Enter, or by partially typing it and tapping on one of the autocomplete suggestions), the onscreen keyboard remains in place.
The behaviour in previous builds (and in my view the desired behaviour) was that the onscreen keyboard disappeared in order not to take up screen space that the web page could use.
被采纳的解决方案
Hi Philip
It looks like you have stumbled upon an unresolved issue in our Nightly build. Until this is fixed, tap the back Android icon (that rotates to a down arrow) to hide the keyboard.
定位到答案原位置 👍 2所有回复 (5)
I should say this doesn't happen when I type a search term (as opposed to a full URL) and tap Enter. Then, the search result page appears and the keyboard disappears.
选择的解决方案
Hi Philip
It looks like you have stumbled upon an unresolved issue in our Nightly build. Until this is fixed, tap the back Android icon (that rotates to a down arrow) to hide the keyboard.
Seburo said
Hi Philip It looks like you have stumbled upon an unresolved issue in our Nightly build. Until this is fixed, tap the back Android icon (that rotates to a down arrow) to hide the keyboard.
Thanks. I've been doing that and it's not a major problem, I can definitely live with it for a few days!
i was already searching in about:config, but could not find the configuration terms. here some browse words i used; (enable text key board tool app on top frontscreen disable timeout) (also can i not copy-paste words from my text board )
Dutch Dummie said
i was already searching in about:config, but could not find the configuration terms. here some browse words i used; (enable text key board tool app on top frontscreen disable timeout) (also can i not copy-paste words from my text board )
I'm still having this problem, after a couple of weeks. Thanks for prompting me to look again at what's going on :)
I found a bug already raised for it: https://github.com/mozilla-mobile/fenix/issues/16668
That suggests it's SwiftKey specific: @Dutch Dummie, are you a SwiftKey user too?