yearRange doesn't work as expected

[mg]

The bug occurs when one uses relative yearRange values with option changeYear: true, for example:

yearRange: '-100:+0',
changeYear: true,

With this example configuration list of years gets broken after date selection:

1. List is 1909-2009
2. We select 1909
3. List is now 1809-1909
4. We cannot select above 1909 - Bug

[BMCouto]

It is a bug indeed, but it can be easily solved with something like:

yearRange: '-120:' + new Date().getFullYear()

Anyway it's something that should be fixed.

Replying to mg:

The bug occurs when one uses relative yearRange values with option changeYear: true, for example:

yearRange: '-100:+0',
changeYear: true,

With this example configuration list of years gets broken after date selection:

1. List is 1909-2009
2. We select 1909
3. List is now 1809-1909
4. We cannot select above 1909 - Bug

[kbwood]

Fixed in r3485. Year range now has three formats: 'c-n:c+n' for years relative to the currently displayed year, '-n:+n' for years relative to today's year, 'nnnn:nnnn' absolute years, and the default value has changed to 'c-10:c+10' to retain backward compatibility. These formats may be mixed for the start and end of the range, e.g. '2000:-5'.