9439 2010-04-06 23:00:59 +0000 UA should not change values of input elements in telephone state 2010-10-04 13:57:48 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED NEEDSINFO http://dev.w3.org/html5/spec/forms.html#telephone-state NE P2 normal --- 1 mounir ian annevk ayg bugs ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 34623 0 mounir 2010-04-06 23:00:59 +0000 According to the specifications "User agents may change the punctuation of values that the user enters." and according to Ian, this means "For example, if I enter "1 650 253-0000", the user agent is allowed to change that to "+1 (650) 253 0000" or "16502530000" or "+1 (650) 253-0000". This is because such reformatting is common practice in telephone number entry fields.". In my opinion, this is the opposite from the note: "Unlike the URL and E-mail types, the Telephone type does not enforce a particular syntax. This is intentional; in practice, telephone number fields tend to be free-form fields, because there are a wide variety of valid phone numbers." Changing the punctuation is part of enforcing a particular syntax. In addition, it may make the check very hard. For example, I can check if a french phone number is valid by adding this in the pattern attribute: "/^0\d{9}$/" If the UA is adding spaces, hyphens or anything else, it will break the check. 34853 1 ian 2010-04-13 01:34:53 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: In practice, telephone number fields reformat the input — that's just how they work. We may have to change that if we find it really doesn't work well on the Web, but I think that it makes sense to start with what the existing practices are. 35034 2 bugs 2010-04-14 20:57:03 +0000 So the current wording allows browser to do whatever to the punctuation. Scripts can't rely on what, nor can server side code. So why to have such "may change" functionality? 35219 3 bugs 2010-04-22 15:37:52 +0000 If the wording stays the same in the specification, could someone at least give good reasoning for such "may" feature, which lets browser to do whatever. 37581 4 ian 2010-08-17 19:06:18 +0000 Is the reasoning in comment 1 insufficient? I don't really understand what you're asking for.