lucy24 - 1:15 am on May 24, 2013 (gmt 0)
...results in a 404 page when clicked from a PC.
"Firefox doesn't know how to open this address, because the protocol (tel) isn't associated with any program."
Now I am confused. Where does the 404 come in?
If the browser steps in before even sending a request to the server, then it isn't your problem. The only way to prevent it is to deploy user-agent detection ahead of time, so the tel: links are only displayed if the user is on the right kind of phone. Or if-- oh, ###, now it gets complicated-- their computer really can make phone calls. (This is a closed book to me, but I have just this moment remembered my father telling me that his computer dials for him. That's a desktop, not mobile-of-any-kind. And no, he's not on a dialup modem connection ;))
You may still be able to treat it as a non-problem if the links are designed so it's very obvious they lead to a phone call, not to another page. Of course there will always be those users who expect their computer to be able to act on all links all the time everywhere...