Treat range inputs the same as number inputs and fixes issue #1189

I've simply added range as to the list of input types that can be treated as a number type. It has the same properties (min, max) and should be capable of behaving exactly the same way.

I'm not too comfortable with the docs/examples yet so I may have done something wrong. Please let me know if I need to fix anything.