Scrolling is not possible when grouping

[JBCodingHash]

index.html

Describe the bug
Hello, I’ve got a strange problem: when I’ve hidden grouped elements and try to scroll, the scroll bar keeps jumping back to the top, so I can’t scroll any further down; and even when I open one, it jumps to a different spot. Have I done something wrong? I’ve uploaded a video and an index.html file with some sample code.

Tabulator Info

• 6.4.0

Working Example
YOU MUST include a link to a JS Fiddle or Codepen that demonstrates the problem, it is very hard to diagnose an issue from a simple description.

To Reproduce
A step by step guide to recreate the issue in your JS Fiddle or Codepen:

1. Go to 'https://jsfiddle.net/3btn7gs8/1/'
2. Try scrolling down

Expected behavior
It must be possible to scroll down easily whether all groups are collapsed or expanded

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• Edge Version 146.0.3856.109

Smartphone (please complete the following information):

• None

Additional context

index.html

[azmy60]

Hey @JBCodingHash , have you seen this bug before 6.4?

[JBCodingHash]

Hello @azmy60
Thanks for the quick reply. Yes, I’m using version 6.2.5, and I noticed this when several groups appeared and I had to scroll. Is there perhaps a workaround, or could you tell me where to look for the error? It’s making the system unusable. I’m happy to help where I can.

[azmy60]

I just checked other issues related to this. You might need to downgrade the version to 5.4.4 to fix it.

There's a PR that might fixes this so next task for me is to look into that and I hope I can merge it soon. :)

[JBCodingHash]

Okay, that's really nice, thanks @azmy60

I can confirm that this issue does not exist in version 5.4.4

[JBCodingHash]

Hello @azmy60 , I’ve seen that there’s already a pull request. May I ask how long it usually takes for something like this to be published? Is there an approximate timeline? Is there anything I can do to help?

[azmy60]

It usually didn't take too long to be published after merging, especially for this kind of bug. But I don't really have a straight answer unfortunately :/

The timeline is up to @olifolkerd because he can release the NPM package. Me and @rathboma are still waiting for his directions.

@JBCodingHash you gave us a heads up by making this issue so that's a help, we appreciate that! Feel free to make PRs as well if you want and then I try my best to review any PRs.

[olifolkerd]

@azmy60 I'm gonna give you and @rathboma nom access this weekend so I'm not a bottle neck

[azmy60]

@olifolkerd Thanks Oli!

[JBCodingHash]

Hi @azmy60 , @olifolkerd I don’t want to bother you first thing on Monday, but is there any news?

Thanks

[JBCodingHash]

Hello @azmy60 , @olifolkerd , I tried using the latest version, but unfortunately found that some parts no longer work. However, as I really need this fix, my question is: Is there a branch of version 6.2.5? I can’t find it here, and I wanted to use that and integrate the fix myself.

Many thanks