User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Build ID: 20170926190823 Steps to reproduce: go to https://www.bing.com and tap on the search bar. I would say about 2 out of 3 times I do this, the keyboard does not open and requires another tap to open it. I've never experienced this in Chrome for Android

Could be related to bug 1404111, although it's hard to say whether it's just similar symptoms, or really a duplicate. In case might be be useful, what phone/OS version are you using?

Oh and yes, I'm seeing something, too.

Pretty sure this is another dup of 1402461

No, I'm afraid not. Visiting www.bing.com and clicking on the search field, the page will enter input mode and the cursor appears in the search field, but the keyboard will frequently not appear. The keyboard does appear if I click into the search field again, or - as far as I can tell - strangely enough ocasionally the first time I visit www.bing.com and click into the search field after starting the browser. So 1. I launch Firefox and visit bing.com 2. I tap into the search box and the page switches to search mode and the keyboard appears (except when it doesn't - hmm). 3. I close the tab and open a new one and visit bing.com 4. I tap into the search box, the page switches to search mode, the cursor blinks in the search field, but the keyboard doesn't appear. 5. I tap the Bing logo to get back to the default view of the page. 6. I tap into the search field to enter search mode and the keyboard still doesn't appear. If I then tap into the search field again, the keyboard finally appears. 7. I dismiss the keyboard and tap on the Bing logo again. 8. I tap into the search field and this time the keyboard appears. 9. Steps 7/8 can be repeated with the same outcome at will. 10. Going back to step 3. starts the whole cycle again.

(In reply to Jan Henning [:JanH] from comment #4) Hmm, I can reproduce this bug on an old Nightly, but not today's, so I am pretty sure it's a dup. Can you still reproduce this with the latest Nightly? How about you, Will?

Yes, both with today's Nightly (which definitively has your patch) and a clean profile, as well as a local build. As I mentioned in bug 1404111, maybe it's something that happens only some devices? On my Moto G4 Play, I can reproduce bug 1404111 (at least my version of it) as far back as Firefox will run on Android M, while on an S3 Mini I cannot reproduce this either.

I'm using a Moto E 2nd gen running Android 6.0, and the issue is still present on Nightly (2017-10-05). Can anyone test on a clean android or google nexus/pixel phone?

[triage] Annoying but non-critical.

Re-triaging per https://bugzilla.mozilla.org/show_bug.cgi?id=1473195 Needinfo :susheel if you think this bug should be re-triaged.

We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly](https://play.google.com/store/apps/details?id=org.mozilla.fenix) an issue can be reported at the [Fenix GitHub project](https://github.com/mozilla-mobile/fenix/). If you want to discuss your report please use [Mozilla's chat](https://wiki.mozilla.org/Matrix#Connect_to_Matrix) server https://chat.mozilla.org and join the [#fenix](https://chat.mozilla.org/#/room/#fenix:mozilla.org) channel.