error while scroll datatable with activeContent

I noted weird behavior when there are two tables with activeContent elements - you can’t scroll (error in console) table
see https://snippet.webix.com/31nilfu9
I’m aware that activeContent is deprecated in 7.0 and you suggesting rewrite with template, but maybe there is some easy fix (we don’t have time for rewrite yet)?

Hey @yurash, I am not really sure about the exact cause of this issue, but it seems that the table needs to be rendered once again, use refresh to achieve this: https://snippet.webix.com/ix8f7ev8.

As you have already mentioned activeContent is becoming deprecated in 7.0, it would be great if you could make a switch to a newer version of Webix at your earliest convenience, since version 4.4 is pretty old at this point.

hmm, your snippet works, but then I modified it so second table have activeContent too (as actually in my real code) and it broke again https://snippet.webix.com/tpkvayur

Seems like only the last active table will work in this case, you can see this here https://snippet.webix.com/4ua5d3w3, where the last selected (active) table will work, the other will not.

Unfortunately, there isn’t a way around this, that was one of the reasons why we are deprecating the activeContent API in 7.0. As you’ve already mentioned in the original post, I can only suggest rewriting your code using complex templates with custom elements instead of activeContent.

yes, I was able to rewrite code with custom elements. For me activeContent deprecation looks like sort of step back. Webix power comes from it’s widgets. Some of those widgets good to have in table/list. In my “active table” I’m using checkboxes/radioboxes/buttons - those are easy to rewrite using builtin templates like “{common.checkbox()}”. Also I’m using counter widget - that took time to recreate and that just not feels right to spend valuable time recreating existing widget. I’m suggesting, when 7.0 is out, you try add counter (also maybe slider/rangeslider/toggle/switch widgets) as built-in “common” templates, or have it implemented in sample template. Otherwise some of your users would feel that you let us down.