Programmers also need a little bit of cost!! IOS input rendering differs from Android, as well as problems caused by automatic phone call functionality

A few days ago the public number was completed for the leadership review, because the public number was developed on the basis of the previous 1.0, so there is no concern about compatibility issues [in fact, ignoring the ios=. = Forgive me for my ignorance]

The result is a problem and there are several problems:

1. The input render effect differs from andriod

2. Long string numbers will be rendered as phone numbers

3. Four decimal places are rendered as hyperlinks

1.input

Android settings do not have rounded corners. No gradients, text centered, absolutely no problem.

By the way iOS becomes this bird!! What the hell is this??

The original safari parsing input[type= "Submit" and input[type= "reset" buttons on the iphone are rendered in the default UI of Apple's browser.

OK, disable off on the line:

{ -webkit-appearance: none;}

2. Long string numbers

And then I met the second pit Daddy thing. iOS identifies long-numbered numbers as phone numbers, and calls contacts

My part of the code is this

    　 <Divclass= "Name">Table name<%=name%></Div> 　　 <div class = "num" >Table Number:<span><%=Address%></span> 　　　　 <span><%= Number%></span> 　　 </Div>

I want to get the NUM value so I wrote:

$ (". Num"). Children ("span"). EQ (1). HTML ()

And then I found out that a bunch of messy code meant that iOS rendered this number as a phone number and added a new span node in front of that number because I was using the EQ (), so it was tragic.

The solution, of course, is to disable the phone call feature

<name= "format-detection"  content= "Telephone=no"/> 

If you need to make a call, just write it.

<href= "tel:15600000000">15600000000</A  >

3. Four decimal places

The third question is probably this, I did not find a good way, but directly to take two decimal places [because this is written by others, there is no estimate of compatibility, and four decimal number of RMB what ghost? ]。 So no solution to the second problem can solve the problem. If someone sees and knows the right solution, please let me know. Thank!

In fact, I used to read a book when I saw a passage:

Since the iOS simulator only runs on your Mac, if you use the Windows operating system, then the best and only option is to buy the iphone to test.

It seems reasonable to say that I am speechless ...

In fact, the above problems I was in the commissioning of the time to borrow a colleague an iphone to debug Ah!!!!

So do I have to think about starting an iphone? Qaq

Okay, there's the simulator.

Programmers also need a little bit of cost!! IOS input rendering differs from Android, as well as problems caused by automatic phone call functionality