Mobile development pitfalls [Continuous updates ...],..

Mobile development pitfalls [Continuous updates ...],..

Now everyone is basically using smartphones. It seems that browsers on mobile phones are also relatively advanced, and they are basically webkit kernels. At first glance, they seem to have seen hope... However, the mobile terminal does not have fewer pitfalls than IE, and debugging seems more difficult because it is not as convenient as PC...

 

A brief summary of several relatively shallow pitfalls that I encountered during development at ordinary times, first pre-push.

 

I. Android mobile phone overlapping area highlight: This is the name of the person on the Internet. It is a shadow when I click it. It is hard to see the function;

Solution: {-webkit-tap-highlight-color: rgba (0, 0, 0 )};

 

The second part is that the browser cannot play audio automatically: This part seems to be a dark indicator of the Apple device (laughing...). No way, the user experience is good, for fear that you harass the user;

Solution: you can capture any user operation and then manually trigger a media playback event;

 

The three Browsers Do not support partial scrolling: The Rolling events on the Mobile End have always been difficult...

Solution: 1. Use the layout to scroll the body and display other elements in dislocation. (not implemented yet ...)

2. Use the third-party iscroll, which is my consistent solution;

 

Four strange input floating boxes: the input box of the type = password type has an additional input box suspended next to the original input;

Solution: Use the type = text input box instead of the password type, and set the style {-webkit-text-security: disc;} to hide the input password;

(Discovering that human wisdom is infinite ~~~)

 

For the time being, although mobile projects are still being implemented, water-related projects are not so deep, so they haven't fallen into any abyss yet... thank you very much for your predecessors!