841943 - Improve the way that we "clamp" the value of <input type=range>

Status: RESOLVED INACTIVE

(Core :: DOM: Core & HTML, defect, P5)

Description

[Jonathan Watt [:jwatt]]

Bug 836314 comment 28 follow-up.

We should improve the way that we "clamp" the value of <input type=range>.

Comment 1

[Jonathan Watt [:jwatt]]

Mounir, can you give me a more concrete description of what you were thinking of here? From our last discussion on IRC you weren't exactly sure. :)

Comment 2

[Mounir Lamouri (:mounir)]

IIRC, I am not a big fan of the way we "sanitize" the value when @max, @min or @step is modified. We use a huge hammer to do something that "might" be easier to do. In other words, we fully sanitize everything but maybe we could have clever assumptions. This is more cleanup than anything else so as long as we pass the tests, I do not think we should block the release of <input type='range'>. However, that would be great if we can do it at some point or at least think about how we could do it.

Comment 3

[Firefox Bug Husbandry Bot]

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.