Summary of Android WebView pitfalls

Recently, I migrated my iPad HybridApp to Android, which has encountered too many pitfalls. This has caused me a headache for the old man who has been tossing Android for nearly four years! Now, let's list all the problems we encountered before and solve our own problems. Now we have solved the android keyboard coverage problem. The most difficult problem below is the adaptation of the screen height! This article will be updated continuously

1. The cause of the Andrid4.1 event penetration BUG is unknown.

2. Android2.X Chinese does not support bold


3. Currently, the WEBVIEW size is 320, 360, 400, and more.


The resolution may be related to the screen size.
Current Test Results
320-resolution
720 resolution-"360
800 resolution-"400

Is it half the width of the mobile phone?

The screen density problem !!!

4. Placing the original size image in the WEBVIEW will be blurred. We recommend that you use a large image to narrow down the image.
For example, to reduce the image size by 300*100, use 600*200.


5. space such as ANDROID 2.X TEXTAREA | INPUT may be displaced due to position: fix.


6. text-overflow: ellipsis; (string CSS truncation) Function BUG: the length of the interception will be calculated together with margin-left, resulting in excessive contents being intercepted by containers containing margin-left.


7. The displacement of translate3d causes the position: fixed's built-in elements to move together. This BUG is even more disgusting because it will be removed directly on the IPHONE, but it can be displayed in ANDROID, but if there is an event, the clickable area of the event will shift. It is estimated that ANDROID has not fixed the problem.


8. The WEBVIEW memory limit is 12 Mb (this problem has not yet occurred)


9. ANDROID2.X does not support BOX-SHADOW.


10. MASK is not supported.


11. Support for CALC. Be sure to avoid being precompiled by LESS
Width :~ "-Webkit-calc (100%-100px )";
Margin: 0px 50px;

Using this method, you can easily center floating elements without calculating the TOP LEFT

12. android4.4 does not seem to support target-densitydpi = device-dpi, and Android4.3 does.