Github user hnilsen commented on the pull request:
https://github.com/apache/cordova-android/pull/105#issuecomment-52066802
I was away on vacation, so couldn't answer to your comments.
I'm back at work, and we've updated Cordova on Android to 3.5.1, in
response to the IBM Research exploit issue, and the problem we're seeing has
returned.
I believe that you're flipping the flag redundantly, and especially Samsung
keyboards send events in a different order to Cordova than other phones
(without messages), which makes the flag turn from true -> true (meaning no
messages are sent between JS and Native).
3.5.1 still has this bug.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
