Uhh... http://input.mozilla.com/search/?q=stephen&product=firefox We should parse for phone number syntax. Some examples of how to do this can be found at http://diveintopython.org/regular_expressions/phone_numbers.html
Really? I think we are getting into a spiral of blocking random stuff now. You know that American phone numbers have a different format than most others in the world?
Ah, I should have been a bit more clear. We shouldn't block all of those instances, but a few more common ones that we're sure won't result in useful types of feedback being blocked. For example, (xxx) xxx-xxxx or xxx-xxx-xxxx. Can you think of a useful form of feedback that might be blocked by the phone number syntax mentioned above?
(In reply to comment #2) > Can you think of a useful form of feedback that might be blocked by the phone > number syntax mentioned above? Not really, but I do think people who ignore the current warning will probably not adhere to a common spelling of their phone number. Likewise, given we are now localizing things, protecting against US-only numbers only seems silly. In short, phone numbers are a case I wouldn't worry about currently.
Aye, I've thought about the l10n piece before and filed the bug even with that use case. You're right though, the cost is a bit too high in terms of investigation. I'm ok with lowering this until we can find a proper implementation for it. We still have the warning message on the submission forms in the meantime.