Scrolling + rendering issues

Tags: #<Tag:0x00007f136b9abac0>
#1

I’m having issues with scrolling on my grid.

I’ve noticed that the ‘viewportRowRenderingOffset’ is a bit buggy.

I have a video showing the problem im getting: https://streamable.com/rkwzo

The problem in this particular case is that I have 70 rows. VERY randomly, the number of rows at the end varies depending on the speed we scroll at, which shouldn’t be the case.

Looking at the video, you can see that the first time i scroll, the last row is #68. IF i scroll up and back down again, you can see rows up to #70.

I’m at a loss as to how to fix this. The last row is very random at the moment and I feel like I have zero control over what row handsontable will stop loading at.

In case you need it, this is how im building my grid:

<HotTable
                afterChange={this.changeCell}
                colHeaders={true}
                rowHeaders={true}
                columns={columnInfos}
                contextMenu={false}
                currentColClassName={'currentCol'}
                currentRowClassName={'currentRow'}
                data={this.state.data}
                fixedColumnsLeft={1}
                fixedRowsTop={0}
                formulas={false}
                licenseKey='xxx'
                nestedHeaders={columnTitles}
                observeChanges={true}
                persistentState={true}
                ref={this.setHotTableRef}
                root='hot'
                viewportColumnRenderingOffset={50}
                viewportRowRenderingOffset={10}
            />

I’ve modified the ‘viewportRowRenderingOffset’ a few times with no luck whatsoever.

Scrolling + Redering Issues part 2
Editing cell is too slow when I use ViewportRowRenderingOffset : 1000
#2

Hi @ssense_dev

you can try to set viewportRowRenderingOffset for a bigger value and then check if that helps.

If it wouldn’t change a thing please create a demo (can be a zip) that I’ll be able to test.

#3

Ok, i’ll try to create a demo later and send it over.

#4

For now @aleksandra_budnik i increased the number to ‘100’ and it seems to be working fine. I will check when our data grows to see if the issue comes back.

Thanks.

#5

OK, great. Thank you for an update.
I think that we can close this issue.

#6