[whatwg] Make stepUp() and stepDown() more developer-friendly
ian at hixie.ch
Tue Nov 20 14:55:52 PST 2012
On Tue, 20 Nov 2012, Scott González wrote:
> Can you explain why these methods should be no-ops if the value is above
> the max or below the min? In jQuery UI, we decided that using these
> methods should always result in a valid value.
I actually missed that in Mounir's suggestion, and the spec now rounds to
the nearest allowed value in that case, rather than doing nothing.
Mounir: is that ok?
> I can list out the steps we take for all conditions, but I'd like to
> hear everyone's thoughts on the various cases where you're suggesting
> that the methods do nothing.
Mostly I agree with Mounir here, but I'm curious about what you think
should happen for the case where there's no value, and the case where the
control isn't a numeric/date/time type. I could see an argument for
stepping from the default in the former case (Mounir, what do you think
about doing that?) but for the latter case I don't really see any point
doing anything but throw an exception, as Mounir suggested.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg