Timeline for What Special characters should one allow for a Phone Number?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 14, 2017 at 10:12 | comment | added | Sebastian Redl | @Ranger That is the exact opposite of what the answer was getting at. | |
| May 10, 2011 at 5:50 | vote | accept | Ranger | ||
| May 10, 2011 at 5:50 | comment | added | Ranger | Oh yeah, i will figure out the countries where our major users live and then i will write some validation code. Thanks All, i appriciate your efforts. | |
| May 9, 2011 at 12:23 | comment | added | Benjol | +1 and most importantly just because a phone number is valid, it doesn't mean it exists, and even if it exists, it doesn't mean it belongs to the person in question... | |
| May 9, 2011 at 10:02 | history | edited | P Shved | CC BY-SA 3.0 | added 59 characters in body; deleted 3 characters in body |
| May 9, 2011 at 7:22 | comment | added | E.Z. Hart | +1 - phone number validation (especially defined this broadly) is often pointless, not future-proof (KL5-6743 used to be a valid phone number, for example), and just annoys users who have special cases. Make you phone numbers a big text field and let the automated dialers (if there are any in this scenario) parse what they can. The exceptions can be raised to humans who can handle the situation appropriately. | |
| May 9, 2011 at 7:06 | comment | added | perdian | +1 for "users just wanted to convey you an important piece of information". I've too often seen unnecessary validation that simply annoys the user without any actual technical (or organizatorical) requirements. | |
| May 9, 2011 at 6:46 | history | answered | P Shved | CC BY-SA 3.0 |