STR: 1) go to https://m.realestate.com.au/buy 2) click in "Search by region..." input Expected: Software keyboard appears Actual: No keyboard. Note: This possibly affects omegle.com and login.live.com (see associated bugs for URLs).

Here's the regression range: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=5424426a71897398c11894f0c43c3e6d485f4604&tochange=44532a19e524df52ccf35fd0e342996027d86342 I assume Bug 1343728 regresses this... (I know it's late to track for 56, but maybe a fix (were it simple) could ride along a dot release).

Is this a fennec only bug? IIRC we don't run e10s there so the usual problem caused by that bug (which is that we spin a nested event loop more often) wouldn't happen. Almost all of the code in that bug should be e10s-only :-/. I tried reproducing on my phone, and it didn't work in fennec nightly, but after updating to the latest nightly (I was probably a couple of weeks out of date - I had the new photon theming to add a maximum oldest version) it started reproducing, which doesn't seem to agree with the culprit being bug 1343728.

login.live.com is - problematic even on 55 (occasionally the keyboard doesn't pop up automatically [1] and you have to try tapping a few times before it appears) - conversely even on 56 and later it's not totally broken - if you tap often enough, eventually the keyboard appears. With https://m.realestate.com.au/buy - I'm seeing this even on 55, but if you tap often enough and/or momentarily background the tab it starts working - on my 58 build on the other hand I haven't been able to get the keyboard to show up at all [1] note that bug 1400878 changed this starting from 57

(In reply to Nika Layzell [:mystor] from comment #2) > Is this a fennec only bug? Possibly... I don't have any other devices with software keyboards. (Just found https://github.com/webcompat/web-bugs/issues/10654 as well -- let me see if I can get a different (??) range on that site)

Let's keep track of this in bug 1404111 for now. You can still request uplift to m-r in that bug if you come up with a good fix.

Given that the webcompat reports are all very recent, they were probably mostly about bug 1402461 in fact.