12915 2011-06-08 17:58:25 +0000 Note that Arabic and Persian Unicode digits could be used through <input type=number> UI 2011-09-26 06:24:24 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified PC All RESOLVED FIXED P2 normal --- 1 ehsan ian annevk ayg ian jackalmage jonas mike mounir public-html-admin public-html-wg-issue-tracking w3 public-html-bugzilla oldest_to_newest 49327 0 ehsan 2011-06-08 17:58:25 +0000 The Arabic and Persian languages use their own Unicode code points for digits (U+0660-0669 for Arabic, and U+06F0-06F9 for Persian, see <http://unicode.org/charts/PDF/U0600.pdf>). Many Arabic and Persian keyboard layouts map those code points to the digit keys on keyboards, to enable users speaking those languages to enter digits in their language. <input type=number> should allow those code points to be entered, and require UAs to treat them as Latin digits for processing and form submission, to make the form control usable to Arabic and Persian users. 49331 1 jonas 2011-06-08 18:21:43 +0000 Technically, this might already be allowed by the spec. Though at the very least it might be a good idea to add a note reminding implementations that this would be a good idea to do. 49361 2 jackalmage 2011-06-09 02:52:10 +0000 This is indeed already allowed by the spec - UAs are allowed to present any interface they want, including one that allows inputting arabic or persian digits, so long as the value is set to a valid number. 49416 3 mounir 2011-06-10 14:27:42 +0000 It's not the first bug opened about <input type=number> i18n and like all of them, I don't think that's a spec issue but much more an implementation issue: the specs only specify the format of the submitted number, I believe the implementations are free to do whatever they want to show it or help the user write it. 49427 4 ayg 2011-06-10 18:13:30 +0000 Concur with Tab and Mounir that this is the sort of thing the spec already allows UAs to do, but it would be nice to have a note suggesting UAs do this. This is a UI issue, so it probably shouldn't be a normative requirement. 53892 5 mike 2011-08-04 05:34:14 +0000 mass-move component to LC1 55012 6 ian 2011-08-15 03:51:04 +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: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. 55014 7 contributor 2011-08-15 03:51:57 +0000 Checked in as WHATWG revision r6451. Check-in comment: Note on UI for type=number. http://html5.org/tools/web-apps-tracker?from=6450&to=6451 55154 8 ehsan 2011-08-15 23:50:54 +0000 + form Romans might display the value in Roman numerals rather than in s/form/for/ Not sure if I should reopen the bug for this... 55205 9 annevk 2011-08-16 08:23:19 +0000 Probably better to file a new bug since the original bug is fixed. 55251 10 ehsan 2011-08-16 23:36:06 +0000 Filed bug 13798.