Ticks callback have unexpected behavior

[olyckne]

As I mentioned here #1021 (comment).

I think the ticks callback have som unexpected behavior.

Let's say I want to show every X label, with something like:

function (label, index) {
    return index % 10 === 0 ? label : '';
}

On some screen sizes it does what expected and in some not.
I guess the algorithm that automatically skips some labels interfere with the callback.
If I'm not mistaken that algorithm counts against the whole ticks array and not the actual showed one?

I have a graph with over 300 data points and want to show 3-5 labels and it really isn't possible with the callback.

Example.
I can live with this many labels

but on a small screen it only showing one:

Even more clear when it shows only one here:

but a little smaller screen and it shows four:

Not a big problem for me since I already have my own custom scale and can implement the afterBuildTicks hook and simply filter the ticks array, but it probably should be fixed.

JsFiddle for the example:

https://jsfiddle.net/olyckne/7ycm5bjg/10/

[etimberg]

There is an auto skipper. Shouldn't be too difficult to disable in this case.

[olyckne]

Yeah. If you have implemented a callback you probably don't want the auto skipper so it could probably be disabled in that case. Another option is an autoSkipper true/false.

[olyckne]

Oh, just noticed the afterBuildTicks "workaround" doesn't work at all.

Maybe it isn't supposed to be used as I did it though.

I simply filtered this.ticks to only contain 4 items, but that means the labels is showing on completely wrong places, and the first four tooltips gets their title from those four items.

afterBuildTicks: function() {
    var everyX = (Math.ceil((this.ticks.length/2)/10)*10);
    this.ticks = _.filter(this.ticks, function (tick, index) {
        if (index === 1 || index === this.ticks.length - 1 ) {
            return true;
        }
        return index % everyX === 0;
    }.bind(this));
}

[etimberg]

Closing since #1810 was merged