We shipped this regression in Firefox 6 and 7 because we didn't realize the extent of the problem in time to back it out. However, with the increase in Nightly/Aurora users we are seeing a ton of duplicate bugs and finding more sites that this effects. We should back out bug 641836 until the regression can be fixed.
Created attachment 562126 [details] [diff] [review]
This is just a complete backout of bug 641836. Requesting approval-mozilla-aurora for Firefox 8. This backs out a change that caused a serious user-visible regression in Firefox 6. See comment 0 for more discussion. I believe this is low-risk; it restores the code that we shipped in Firefox 4 and 5.
Comment on attachment 562126 [details] [diff] [review]
I agree that backing this out will (hopefully) result in fixing many recently filed keyboard bugs.
The IME code is being rewritten, so hopefully we can address the original bug a little better.
Let's get this on trunk ASAP so we can do some quick tests.
Landed on Beta for Firefox 8:
Virtual Keyboard is triggered when opening an Etherpad webpage on the latest Beta build. I'm able to change the name and to chat, but when I tap on the Etherpad body, the Vkb is still displayed, but the cursor is missing. If I hit any character key in this case, nothing is typed on the left side. Should I close this issue as verified fixed?
Mozilla/5.0 (Android;Linux armv7l;rv:8.0)Gecko/20110928
Device: Samsung Galaxy S
OS: Android 2.2
(In reply to Cristian Nicolae (:xti) from comment #6)
> Virtual Keyboard is triggered when opening an Etherpad webpage on the latest
> Beta build. I'm able to change the name and to chat, but when I tap on the
> Etherpad body, the Vkb is still displayed, but the cursor is missing. If I
> hit any character key in this case, nothing is typed on the left side.
> Should I close this issue as verified fixed?
Yes, please. File separate bugs (if they are not filed yet) for Etherpad issues other than the keyboard not appearing.
Based on previous 2 comments, marking as verified fixed.