> > > The goal of fool-proofing phone fields is a quite noble one but, let's > be honest: it's quite near to an utopia. Any "solution" that may cause > valid inputs to break is definitely bad. If fixing wrong inputs risks > valid ones to break, we are not only not solving the problem, but we > are moving it somewhere it doesn't make sense: if you had to choose > between wrong inputs breaking or good inputs breaking, is there any > sane reason to chose the later? >
This is what I was saying. It is noble, but utopic (Yeah, you put it better in words). But now I realized: UA handling of type=tel is just a possibility, not a mandatory feature. Thus, I think even it is documented in somewhere in HTML 5 spec, it won't be used/implemented at all due to all the drawbacks we were discussing about in this thread. -- Hugs, Davis
