We want a gaia-ui test for this bug to make sure this is catched by automation. Ideally, we would like to also have this catched by b2g desktop. But that bug didn't happen on b2g desktop, because the keyboard is normally out-of-process. For b2g desktop, we would like to get the keyboard in-process then, for this test. For more info, see bug 1121033, comment 13: "Ah, PBylenga provided me some info over email, and it seems I have to bump the Flame memory down to 319 MB to make this reproduce, because that forces the keyboard to be in-process. I'll back out 1119497 for now, and will re-land it once I've figured out how to fix this."

Marking WONTFIX, sorry for the bug spam. If somebody still wants to work on this, please file a new bug for it.