adrianszymanski89

Hi @gl-aagostino Thank you for contacting us and reporting this issue. I'll report it internally for further investigation and update you once the fix gets on our roadmap.

Hi @vzotov Thank you for your input and additional examples. Indeed, the reason for this behavior seems to be the same as in the first case.

Hi @vzotov Thank you for your input. Both reported issues are connected to recalculating the table's dimensions. That's, in general, a known issue for us and is broadly discussed here:...

Hi @rmlevangelio Thank you for reporting this. We will take care of this issue in the next sprint. We will update this thread once it's released.

Hi @leerodgers I sent you a response through our support mail, but to give an update to anyone interested - we haven't put this issue on our roadmap yet. Once...

Hi @dragoshzava We don't have any updates yet. You can send us your license ID so we can check your current support plan and see what options we have.

Hi @dragoshzava We apologize for the delay. We still need to set a timeline for this issue as we focused on other pre-planned projects. We checked for possible workaround but...

Hi @emadebManyDesigns Thank you for reporting this. I was able to reproduce the issue with the larger dataset, as you mentioned, where the problem is visibly easily: https://jsfiddle.net/handsoncode/jdo0qu96/ I'll report...

@emadebManyDesigns Thank you for more details and the workaround. It will surely be helpful for our develops during the investigation of the issue.

Hello @arfis Thank you for reporting this. Indeed, the behavior here is not as should be expected during resizing. I'll report this issue internally, and I'll update you once we...