Android WebView HTML input keypress doesn't fire

Question

On some devices (mostly Samsung, but others too) and combinations of: Android version, WebView version (even with the evergreen WebView in Android 7) and keyboard, there are a number of issues:

keypress isn't fired
keydown and keyup always contain keyCode=229
keypress and input are fired but don't contain the key
textInput isn't fired
maxlength attribute isn't honored on input[type=text] while the user types (more than maxlength chars are allowed and the input is validated only when the form is submitted)

Is there a way to fix these issues?

gabrielmaldi · Accepted Answer · 2022-09-07 23:17:31Z

7

I found that if you extend WebView and override onCreateInputConnection, all of those issues are fixed:

public class WebViewExtended extends WebView {
    @Override
    public InputConnection onCreateInputConnection(EditorInfo outAttrs) {
        // This line fixes some issues but introduces others, YMMV.
        // super.onCreateInputConnection(outAttrs);

        return new BaseInputConnection(this, false);
    }
}

Before overriding onCreateInputConnection:

After overriding onCreateInputConnection (g was pressed):

edited Sep 7, 2022 at 23:17

answered Jul 25, 2017 at 20:06

gabrielmaldi

2,1962 gold badges23 silver badges39 bronze badges

Sign up to request clarification or add additional context in comments.

5 Comments

VH-NZZ Over a year ago

Seriously: thank you just about a million times 🙏🏻. What did you mean by "fixes some issues but introduces others, YMMV."?

gabrielmaldi Over a year ago

@VH-NZZ glad this helped you. Initially, without the super call, we found that sometimes the user would open a numeric keyboard in another app, and when returning to our app, only that same numeric keyboard would be opened for any field, even if for text fields. The super call fixed that for us. But it introduced a problem in some specific devices (can't recall which) where typing wouldn't work: the user would hit the keyboard and nothing happened. That's why your mileage may vary and you should test if this solution works for your specific scenario.

VH-NZZ Over a year ago

Cheers for this explanation mate. This is a bit of a pain to manage but luckily the user base I'm target is around 20 and all use the same hardware.

SqAR.org Over a year ago

Tried this and it wasn't working initially. Until I found this: medium.com/mobile-app-development-publication/… Point 4: You'll have to add android:focusable="true" and android:focusableInTouchMode="true"to your mark-up to make it work. At least at Android API Level 26 and above.

AndrewS Over a year ago

This would seemingly prevent IME from working - at least that's the result that I see when I try this.

Collectives™ on Stack Overflow

Android WebView HTML input keypress doesn't fire

1 Answer 1

5 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

5 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related