Update: This was a bug which has been fixed by now (Chrome 18).
I have a <input type="range">
and I'm trying to set its value by jQuery. That basically doesn't do anything.
Then, I tried hiding/showing as I thought it would be a drawing problem, but to no avail did I so.
Lastly, I hid the <input>
and showed it using show(1)
, which would mean a fading-in of 1ms. This did set the value, however after doing so the <input>
isn't draggable anymore.
I made this fiddle up: /.
Does anybody have an idea of what's going on here? I'm using Chrome 10.
Update: This was a bug which has been fixed by now (Chrome 18).
I have a <input type="range">
and I'm trying to set its value by jQuery. That basically doesn't do anything.
Then, I tried hiding/showing as I thought it would be a drawing problem, but to no avail did I so.
Lastly, I hid the <input>
and showed it using show(1)
, which would mean a fading-in of 1ms. This did set the value, however after doing so the <input>
isn't draggable anymore.
I made this fiddle up: http://jsfiddle/MhDf7/2/.
Does anybody have an idea of what's going on here? I'm using Chrome 10.
Share Improve this question edited May 6, 2012 at 20:31 pimvdb asked Mar 13, 2011 at 15:38 pimvdbpimvdb 155k80 gold badges311 silver badges356 bronze badges 5- 3 Reproduced. That looks like a Chrome or Webkit bug. – SLaks Commented Mar 13, 2011 at 15:43
- @SLaks: Thanks. Would you remend reporting it to Chrome or perhaps to jQuery? – pimvdb Commented Mar 13, 2011 at 15:47
-
3
It's not a jQuery bug; it also happens when setting
[0].value
. Yes. – SLaks Commented Mar 13, 2011 at 15:48 - UPDATE: They are all fixed now. Tested in Chrome 20. – Derek 朕會功夫 Commented May 6, 2012 at 20:08
- @Derek: Indeed, thanks. It also works in Chrome 18 so I'll update the question. – pimvdb Commented May 6, 2012 at 20:30
2 Answers
Reset to default 6It seems to be a browser bug. The exact same thing happens when using MooTools (DEMO) or when using vanilla JavaScript (DEMO).
However, even if the display isn't updated, the form still submits the correct value.
You might want to fill a bug report... On your jsFiddle page, do the following:
- Click the Page menu .
- Select Report a bug or broken website.
- Choose an issue type from the drop-down menu. The web address of the webpage you're on is recorded automatically.
- If possible, add key details in the 'Description' field, including steps to reproduce the issue you're experiencing.
- Keep 'Send source of current page' and 'Send screenshot of current page' checkboxes selected.
- Click the Send report button to report a Google Chrome bug.
Doesn't work on Chromium 18 and the problem is still there. Seems like Chrome and Chromium version updates are not the same.