Bug 838256 will include styling for <input type=range style="-moz-appearance:none">. Once that has landed and people get to see it, no doubt some people will want to change the default styling. This bug is where that conversation should take place, and the style changes we decide upon should be made. Note that the pref dom.experimental_forms_range will have to be set to true to enable the WIP type=range support.

The dom.experimental_forms_range is now enabled.

When I spoke to dolske in #ux he said the -moz-appearance:none styling I gave <input type=range> basically looks fine. Nevertheless, this should probably have UX thoughts in a more permanent communication channel, so requesting needinfo. (There's not really any rush for this, since we'll release with native theming, and any content authors turning that off will be giving the elements the style they want.)

Given comment 2, we're good to release as-is in this regard I think. I still would like UX input though, so moving to blocking 853822 rather than closing.

(In reply to Jonathan Watt [:jwatt] from comment #2) > When I spoke to dolske in #ux he said the -moz-appearance:none styling I > gave <input type=range> basically looks fine. Nevertheless, this should > probably have UX thoughts in a more permanent communication channel, so > requesting needinfo. Yes I think what we have looks ok. I feel like all of our form controls could use some UX attention though. I would like to spin-up a project that reevaluates the default visuals and strings as well as designing UI for inprogress stuff like type=date. I put together this page just for an overview of the current status of things: http://people.mozilla.com/~shorlander/files/html5-forms/form-controls.html

Okay, well it sounds like this is works-for-me then, and that project for a general redesign of the form controls can take care of any future tweaks. Thanks, Stephen.