<input type=number> coming to Mozilla

The support for <input type=number> that I've been working on for Mozilla is now turned on for Aurora 28 and Nightly builds. If you're interested in using <input type=number> here are a few things you should know:

• The current support should first ship in Firefox 28 (scheduled to release in March), barring any issues that would cause us to disable it.
• As of yet, locale specific user input is not supported. In other words user input that contains non-ASCII digits or a decimal separator other than the decimal point (for example, the comma) will not be accepted. If this turns out to be unacceptable then we may have to turn off support for Firefox 28, or else add a hack to at least accept comma. Ehsan has just finished battling to get ICU integrated into gecko's libXUL, so I should be able to fix this properly for Firefox 29.
• Unprivileged content is not currently allowed to access the CSS pseudo-elements that would let it style the different internal parts of the element (the text field, spinner and spin buttons). The only direct control content has over the styling of the internals is that it can remove the spinner by setting -moz-appearance:textfield; on the input. (The logic and behavior that defines <input type=number> will still apply, just without those buttons.)

If you test the new support and find any bugs please report them, being sure to add ":jwatt" to the CC field and "<input type=number>" to the Summary field of the report.

Tags: Mozilla

<input type=range> coming to Mozilla

I've been working on adding support for <input type=range> to Mozilla. This work is progressing well and <input type=range> is now turned on in the latest Nightly builds to help gather feedback from content authors. If you're interested in <input type=range> I'd love it if you could try it out and report any problems/make enhancement requests. Be sure to mention "<input type=range>" in the Summary field of any reports that you file, and add ":jwatt" to the CC field. I'm currently on vacation but I'll work through any issues that are reported once I get back next week.

To allow content author's to style <input type=range> there are currently two pseudo-elements, ::-moz-range-track and ::-moz-range-thumb. Very rough WIP documentation is here.

Known issues:

• the default CSS styled appearance still needs work, and native theming (giving the slider the appearance of the operating system's theme) is still to come
• vertical slider support is currently disabled until we decide how to allow authors to specify that they want a vertical slider (www-style discussion)
• @list/<datalist> is not currently supported
• there are rounding issues when the range's steps have fractional values

Tags: Mozilla