| TheDJ | |
| May 21 2013, 7:49 PM |
| F10490: Screen_Shot_2013-05-21_at_11.10.58_PM.png | |
| Nov 22 2014, 1:22 AM |
screenshot of the year field in contributions
This is a known upstream issue in Safari (specifically 5.1.x) and some versions of Chrome.
Not sure if it warrants workarounds at our side.
https://bugs.webkit.org/show_bug.cgi?id=62939
https://bugs.webkit.org/show_bug.cgi?id=93236
Version: unspecified
Severity: normal
URL: https://bugs.webkit.org/show_bug.cgi?id=62939
attachment GrutContribQuery.png ignored as obsolete
Current versions of Safari (6.0.4) and Chrome (26.0.1410.65) do not exhibit this bug.
On the buggy version, does the comma end up in the submitted value or is it a display issue only? If a display issue only I wouldn't bother; it'll only affect people running a previous version of Mac OS X or failing to install updates.
I tested with url http://jsfiddle.net/gsAGZ/embedded/result/
- HTML
<input type=number value=5000>
<pre>--</pre>
- JS
$('input').on('change blur click', function () {
$('pre').text(this.value);});
In Chrome 26, type=number is supported and displayed and submitted without any separators.
In Safari 4.0 (Mac OS X Snow Leopard, BrowserStack), input=number is not supported and is treated like a regular text input.
In Safari 5.0 (Mac OS X Snow Leopard, BrowserStack), input=number is supported and is displayed and submitted without any separators.
In Safari 5.1 (Mac OS X Snow Leopard, BrowserStack), input=number is supported and is displayed with separators and submitted without any separators.
