Open Bug 841946 Opened 8 years ago Updated 3 years ago
Consider not going into the error state when @max < @min for <input type=range>
Bug 836314 comment 28 follow-up. It would probably make sense to change the way that we handle @min/@max when @max < @min. Currently that means that we suffer from overflow. We should bring up the idea in the WHATWG of not going into the overflow error state in this case. Mounir will email them.
Some code is checking that minimum < maximum. If this bug got solved, we should fix it.
I'm not really sure I agree that we should do this. In any case, this would require changes to the spec, so moving this out from blocking the initial release to blocking bug 853822.
Mounir, if you think we should do this, can you follow-up in the whatwg list? If the spec is going to change, it would be better to have that done sooner rather than later so we can ship something consistent with that. That said, it's probably not too urgent since this is a pretty darn far out edge case.
http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2013-April/039383.html Given that Chrome implements that proposal, unless there are objections, we should probably just implement it too.
https://bugzilla.mozilla.org/show_bug.cgi?id=1472046 Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5. If you have questions, please contact :mdaly.
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.