kulkarnivshamanth@, I am not sure if this device has Play Store, but still asking for which WebView based app are you talking about, if possible please link a Play Store link for the app. Also, you have a very old Chrome/WebView version M62 (almost 10 months ago from now), is that possible for you to update it to newer version to test it out?

This device Zebra MC3300 (since searching on Google with "Zebra MC33" gives me this) has a physical T9 keyboard, it is based on Android 7.0 (Nougat) AOSP GMS [1], so even we could fix this issue, these users won't get an update unless this vendor is going to update WebView on this device. Besides, I doubt we have such device to test it out, which is very unfortunately..

[1] https://www.zebra.com/us/en/products/mobile-computers/handheld/mc3300.html 

Hi changwan,

Thanks for replying. The issue is occurring on google chrome. And i completely agree with you with the fact the vendor has to update the code. But the problem is i checked the aosp source tree and the webview source code is closed source from nougat. I have previous versions of the same device and i ended up modifying the view and adding the multi tap key support myself. So even if i go to the vendor they wont be able to do anything as they wouldn't have the code for it as well.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

If the keyboard is using a standard Android platform feature that we aren't supporting properly, we will need either more information on exactly what that feature is, or access to a device that uses it so that we can investigate - I can't find any documentation about this, so it's hard to know how to fix this.

If it's a customisation to the Android platform on this specific device, then unfortunately the vendor will have to also customise their WebView to implement support for it - we can't support nonstandard android APIs.

WebView is *not* closed source in any version. The source code is not distributed with Android any more because there is no longer a special, modified version of the Chromium code to build WebView - it's built from the unmodified Chromium source code, which can be checked out and built using the normal processes and tools for Chromium. There are prebuilt binaries provided in the AOSP tree for the convenience of people who don't want to customise WebView and just want to build a working AOSP image, but you do not have to use the prebuilt binaries, and we *expect* device vendors to build their own WebView binaries (from the latest stable version of Chromium), and ideally also to update it every six weeks when new versions are published. There is a README next to the prebuilt binaries that explains exactly what build settings and version was used to produce that binary, and links to the documentation on how to build it yourself.


You say you've modified the view before to add support yourself - if you can link us to the documentation you referred to for this, or give us a copy of your changes, that would be a good starting point to investigate.