Issue metadata
Sign in to add a comment
|
Input[range] stops updating the input value on step change when the input value has been modified intitially
Reported by
mjsta...@gmail.com,
Aug 1 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 Example URL: http://plnkr.co/edit/NPasq5CkStJdCRbEHPuQ?p=preview Steps to reproduce the problem: the test case in the plnkr should be self-explanatory. Here are the manual steps: 1. Create a range input with a step value of 10 2. Change the input value to 5 (via element.value) // value changes to 10 because of step 10 3. Change the step attribute to 6 What is the expected behavior? The value should now be 12. What went wrong? The value is still 10, and the stepMismatch error is set = true Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? N/A Does this work in other browsers? Yes Chrome version: 52.0.2743.82 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 22.0 r0 subsequent changes to the step attribute also cause no value change. This works as expected in FF 47.0.1 and Edge 25.10586
,
Aug 1 2016
It looks like this is a different test case but the same cause as issue 633074 . |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mjsta...@gmail.com
, Aug 1 2016