Home/ Questions/Q 4045156
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-20T13:23:07+00:00

Update: This was a bug which has been fixed by now (Chrome 18). I

  • 0

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.net/MhDf7/2/.

Does anybody have an idea of what’s going on here? I’m using Chrome 10.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    It 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:

    1. Click the Page menu .
    2. Select Report a bug or broken website.
    3. Choose an issue type from the drop-down menu. The web address of the webpage you’re on is recorded automatically.
    4. If possible, add key details in the ‘Description’ field, including steps to reproduce the issue you’re experiencing.
    5. Keep ‘Send source of current page’ and ‘Send screenshot of current page’ checkboxes selected.
    6. Click the Send report button to report a Google Chrome bug.
    • 0