We should remove the decimal example from the demo, and document that step should be an integer to avoid floating point errors.

If someone comes up with a real-world need for decimal increments they should probably just extend the class and use a mapping function to generate non-integer steps (e.g. f(x) -> x/10) ) - if it's useful we can upstream it.

Short of pulling in a decimal type library we're not going to be able to mimic non-integer steps in JS and that seems overkill for a rarely used feature.

...or you could call stepUp()/stepDown() to exploit the native browser functionality, but support is sketchy? https://developer.mozilla.org/en/docs/Web/API/HTMLInputElement

In T102128#3492560, @Esanders wrote:

...or you could call stepUp()/stepDown() to exploit the native browser functionality, but support is sketchy? https://developer.mozilla.org/en/docs/Web/API/HTMLInputElement

I think it covers all our JS supported browsers these days: https://caniuse.com/mdn-api_htmlinputelement_stepup