Range definition max before min

[vogtm]

Hi,

I might just found a little bug.

When you define the max value before the min value within the range object, the initialization will fail.

Have a look at the fiddle: http://jsfiddle.net/KvjSb/

I think when there is object used it should not be depended on the order of the values inside of the object. Looks like a artifact from version 5 initialization.

Best Regards
Matthias

[leongersen]

Jep, the order shouldn't matter, but it does. The object should be sorted internally as min >> percentages >> max. Should not to be too tough to add, but I doubt this is a major showstopper.

Thanks for reporting, I'll look into it!

[vogtm]

You are right, it's no major showstopper. Just a bit confusnig if you run into it.

[leongersen]

This is fixed in #393!

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.