<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - input[type=number] does not accept integers with trailing decimal characters"
href="https://bugs.webkit.org/show_bug.cgi?id=148867#c4">Comment # 4</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - input[type=number] does not accept integers with trailing decimal characters"
href="https://bugs.webkit.org/show_bug.cgi?id=148867">bug 148867</a>
from <span class="vcard"><a class="email" href="mailto:krollin@apple.com" title="Keith Rollin <krollin@apple.com>"> <span class="fn">Keith Rollin</span></a>
</span></b>
<pre>Updating the bug to reflect the result of some analysis. The test case in the original report turned up five tests that were marked as FAIL. Four of them also failed in Firefox and Chrome, and so were considered behavior that we wanted to keep in the name of compatibility. The remaining case -- one that reported that "1." should be considered invalid -- failed in Safari and Chrome, but not Firefox. Upon considering that case, taking into account general usage, conventions in other languages, cross-browser compatibility, and general usefulness -- we've decided to keep the current behavior of treating "1." as valid.
It turns out that the HTML spec is ambiguous with regards to whether or not "###." should be considered valid or not. A bug has been filed to track this issue (<a href="https://github.com/whatwg/html/issues/250">https://github.com/whatwg/html/issues/250</a>).
That aside, upon further testing, we noticed that attempting to subsequently change the value with the up/down arrows in the UI or the stepUp/Down methods on the input object failed. These operations considered any number with the form "###." as zero and so incremented them to "1" or decremented them to "-1". This bug now addresses that issue.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>