- From: <bugzilla@jessica.w3.org>
- Date: Wed, 29 Feb 2012 19:51:13 +0000
- To: public-html@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16165
Summary: i18n-ISSUE-136: Recognition of number formats in
Number state
Product: HTML WG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: HTML5 spec (editor: Ian Hickson)
AssignedTo: ian@hixie.ch
ReportedBy: ishida@w3.org
QAContact: public-html-bugzilla@w3.org
CC: mike@w3.org, public-html-wg-issue-tracking@w3.org,
public-html@w3.org
4.10.7.1.13 Number state
http://www.w3.org/TR/html5/number-state.html#number-state
"The algorithm to convert a string to a number, given a string input, is as
follows: If applying the rules for parsing floating point number values to
input results in an error, then return an error; otherwise, return the
resulting number."
Does this refer to conversion of the text the user inputs into the field, ie.
if the user types in
12.345,67
will the rules for parsing floating point number values be applied to that to
determine whether or not that is a valid number?
Or does this apply only to interpretation of the attribute value or the value
passed to the value by the browser after interpretation of the user input? I
assumed that this is the case, but it isn't clear.
I think a note would be useful, both here and for other states where formats
vary around the world, to clarify this and btw to remind browser developers
that the normal way of representing numbers differs around the world and they
will should expect to have to convert the user input to the expected internal
representation (but not change the user's input itself).
--
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Thursday, 1 March 2012 14:12:11 UTC