Michael Hohner Reporter
	Description • 10 years ago

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0 (Beta/Release)
Build ID: 20140212131424

Steps to reproduce:

Applied CSS style to input element of type=range. The only property that was changed is "border". The property value is "medium none", which is also the default value for the element according to forms.css. So nothing of the element's style was actually changed.


Actual results:

Appearance of element changes completely and unexpectedly. Without style it's a shadow'ed line with a pointed knob, with style it's a solid line with a rounded knob.


Expected results:

Only applied style should change.

	Boris Zbarsky [:bzbarsky]
	Comment 2 • 10 years ago

Isn't this the standard thing where once you change parts of the control that the OS theme engine draws we can no longer use the OS theme engine to paint the control and have to fall back to painting it ourselves?  How similar that looks to the OS theme rendering will then depend on the exact OS theme you use and whatnot.

	Jonathan Watt [:jwatt]
	Comment 3 • 10 years ago

Yes. Although since the native themes don't draw a border for range controls, we could probably make an exception for range.

	Michael Hohner Reporter
	Comment 4 • 10 years ago

The border was just an example. For other properties, e.g. the background color, I would expect the same, i.e. only the background color should change, and not everything else, too.

	Momdo Nakamura
	Comment 5 • 9 years ago

This test case is applying background-color property to input type=range.

	Momdo Nakamura
	Comment 6 • 9 years ago

This is a screenshot of test case 2 (Firefox/42.0 on Windows 10 x86-64).