I filed this because of discussion in bug 747492. Chris mentioned this is likely a regression from bug 707353. Steps to reproduce: - Tap on any Flash embed you see Expected result: - No virtual keyboard comes up (when it's not expected, which it usually is) Actual result: - Virtual keyboard appears. It happens with every Flash embed, not just full page plugins, so this one too: http://people.mozilla.org/~mwargers/tests/plugins/flash/flashembed.html Tested on the Samsung Galaxy Nexus and the Samsung Galaxy SII.

I think this should be a release blocker because interacting with any Flash content will open the VKB. The Flash content will still work correctly, so I don't think this bug needs to be a beta blocker.

I've got a fix for this coming

Comment on attachment 618666 [details] [diff] [review] Fix hiding the keyboard from Flash on Android [Approval Request Comment] Low risk, fixes highly visible bug, mobile only

This is on Aurora and inbound, correct? Is there a link to the changesets for those?

https://hg.mozilla.org/integration/mozilla-inbound/rev/7b04b6bc7e4e https://hg.mozilla.org/releases/mozilla-aurora/rev/8d74d509b936

I am not seeing the issue at http://people.mozilla.org/~mwargers/tests/plugins/flash/flashembed.html. However I am seeing a similar behavior at studio1290.com. I logged Bug 750229 for it. Leaving this issue unverified until it can be determined if the 2 issues are related.

Verified fixed on Nightly 15.0a1 (2012-05-03) using http://people.mozilla.org/~mwargers/tests/plugins/flash/flashembed.html Samsung Galaxy SII (Android 2.3.4)

This is not fixed on Nightly/Aurora. Using Aurora (05/08), Nightly (05/08) STR: www.hulu.com, activate the main container - see virtual keyboard pop-up.

Nevermind, it's the search box on the top right

It still happens on trunk with the url testcase (which is a standalone Flash file).

Ok, I guess that is bug 747492 and/or bug 750771.

Ok, marking fixed, since this was fixed with the urls that this bug was originally about. The other vkb issues are covered by the bugs I mentioned in comment 13.