13689 2011-08-06 03:33:33 +0000 Floating point numbers beginning with a dot should be valid and parsed correctly 2011-10-05 18:08:42 +0000 1 1 1 Unclassified HTML WG HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#floating-point-numbers P3 normal --- 12220 1 contributor ian ayg ian jonas mike mounir Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 54283 0 contributor 2011-08-06 03:33:33 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-microsyntaxes.html#valid-floating-point-number Multipage: http://www.whatwg.org/C#floating-point-numbers Complete: http://www.whatwg.org/c#floating-point-numbers Comment: Is it intentional that floating point numbers beginning with a dot are not a valid floating point numbers? It took a fair amount of reading through the spec to figure out why <input type="number" step=".5"> doesn't do what it looks like it should do. <input type="number" step="0.5"> of course works. Posted from: 69.251.188.87 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7) AppleWebKit/534.48.3 (KHTML, like Gecko) Version/5.1 Safari/534.48.3 54293 1 ian 2011-08-06 03:55:27 +0000 Yes, it is intentional. Maybe it should change? 54370 2 Ms2ger 2011-08-07 20:54:54 +0000 Looks like Gecko already does this: <http://software.hixie.ch/utilities/js/live-dom-viewer/?%3C!DOCTYPE%20html%3E%0A...%3Cprogress%20value%3D.7%3E> 54381 3 ayg 2011-08-08 14:40:01 +0000 Seems like something that should change -- there's no reason to make this invalid that I see. 54412 4 ian 2011-08-08 21:49:56 +0000 Opera also. Not WebKit. 55608 5 jonas 2011-08-22 20:34:40 +0000 It's been brought up elsewhere that we should just use the same algorithm as ECMAScript uses to parse floats. This seems like a good idea to me and would fix this issue. 55613 6 ayg 2011-08-22 20:57:35 +0000 That's bug 12220 -- which is currently WONTFIX, so you should probably reopen it if you want it fixed. I just looked again and discovered that this actually does affect implementer requirements, not just author requirements. ".5" isn't just invalid, parsing it returns an error. This seems very surprising. From the summary, I thought it was just an authoring requirement. 57855 7 ian 2011-10-05 18:08:29 +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. 57856 8 contributor 2011-10-05 18:08:42 +0000 Checked in as WHATWG revision r6635. Check-in comment: Allow omission of the number before the period in a floating point number. http://html5.org/tools/web-apps-tracker?from=6634&to=6635