The problem is probably related to double scrolling.
Because the iFrame has more content than it can handle, touch events are used to scroll through the iFrame. But the webview itself can also scroll, so there is great potential for weird behavior.
See what happens when the contents of the iFrame hit the edge (the user scrolls all the way up or down the iFrame). What happens if the user continues scrolling the iFrame? Should it do nothing and is there an event? Refuse iFrame scroll content? Pass an event into a web view so that it can scroll instead?
This is an ambiguous situation. The way Android responds may be incompatible based on different touch gestures, and may even differ from one version of Android to another.
You better avoid an iFrame and just change the contents of the webview directly, or give 100% the height of the iFrame and 100% width so that it occupies the entire webview.
This will prevent scrolling conflicts, and Android will no longer be confused about where to place the cursor.
Dan m source share