minute and second stepping may make more sense with min=0 and max=60

[taivo]

This is in regard to the datetime component. Currently, the minute and second stepping seems to be tied to minDate, and that leads to a somewhat strange situation. Suppose stepMinute is set to 15, and minDate happen to be 2-Dec-2014 4:02 PM, the minute steps end up being 2, 17, 32, 47.

The work around is setting the minute and second components of minDate to be divisible by stepMinute. This issue is not readily observable when minDate is not specified because the default minDate value has zero for its minute and second components.

I wonder if it makes more sense to just lock the variables minM and minS in datetimebase.js (around line 101) to zero?

[dioslaska]

We need to support both behaviors (see #204).

Added a new steps setting, example usage:

steps: {
    hour: 1,
    minute: 15,
    second: 5,
    zeroBased: true
}

zeroBased is false by default to avoid backward compatibility issues.

stepHour, stepMinute, stepSecond still works if steps not specified, but is deprecated.

[dioslaska]

Added in 2.14.3