Bug: Spans + areaselect + filtering in a datatable

Hello,

I found a bug when using several properties of this powerful library:
http://webix.com/snippet/cabacf8b

In this example you cannot select an area. You can select an area if you don’t filter data or disable spans. But it doesn’t work if you use the three features.

Thanks!

Hello,

the issue is caused by filtering that removes all rows except one. Spans are set with the height 4. That is the issue - spans size appears incorrect after filtering.

http://webix.com/snippet/a1fbd7d2

If you are using rowspans, you should change spans after filtering and sorting.

However, if you are using rowspans to increase the height, there is a different way:

http://webix.com/snippet/f57d1fac

Spans are working well when I sort the data, so the bug is only happening when filtering. I find changing spans after filtering is an ugly way for avoiding this bug.

Anyway, looking at the API,
http://docs.webix.com/api__refs__ui.datatable.html
how can I Know if a certain row is being shown after filtering? (Obviously, without evaluating again filtering conditions)

You can use each method of datastore:

http://webix.com/snippet/3d84bbdb

Using ‘each’ method to rebuild spans after filtering don’t fix the bug:
http://webix.com/snippet/e23cf124

In that snippet I am also trying to remove prev spans because they may be causing the problem, but it didn’'t work neither.

By the way, I am not using spans to increase row height, I am using them to organize data properly.

In that snippet I am also trying to remove prev spans because they may be causing the problem

It seems that you did not remove all the spans. Here is the demo with all spans removed:

http://webix.com/snippet/f07394e2

Ok, thanks. So removing previous spans fixes the problem.