[GH #500] Nested headers UI mismatch after hiding a column and rebuilding headers via updateSettings()

Questions
,
1

Body
Hi Handsontable team,

We found an issue when using a custom flow to hide columns and rebuild nested headers.

This does not happen with the default Handsontable nested headers behavior.
It appears only in our case where we must rebuild and re-render nested headers dynamically.

Steps to reproduce

  1. Hide a middle column (example: visual column index 4, column E).

  2. Observe:

    • console shows correct hiddenVisual and next nested headers,

    • UI still hides/misaligns more than expected.

Expected

After hiding column E, only that column should be removed and parent group colspan should update correctly in UI.

Actual

Even though nestedHeaders passed to updateSettings() is correct, UI renders incorrect nested headers (more than one column/group appears affected).

Question

Is this a known limitation/bug in dynamic nested-header rebuild after hide/show?
Is there a required API/order beyond updateSettings() + render() to force full nested-header recalculation and repaint?

JS fiddle: https://jsfiddle.net/ex3quj02/1/

Handson version: 16.2

Nested headers UI mismatch after hiding a column and rebuilding headers via updateSettings()
2

Hi @sagun.saluja1

Thank you for reaching out to us. We have this issue reported internally. I added your report there and will let you know as soon as I have any updates.

3

Hi Adrian, hope you’re well. I work with Sagun (the original poster in this thread).

From your reply, I understand that this issue was already identified internally, and you have added our report to that existing issue. Can I please check when this was originally logged, as we need to get an idea of how long it may take to fix, since it is affecting our possible options for some improvements we’re aiming to add to our existing customer-facing solution.

Many thanks, Blake.

4

Hi @blake.gilchrist

This issue isn’t on our roadmap yet, but I hope we will be able to fix it in the nearest future. I will update this topic as soon as I have more information.

5

Ok, thanks. We’ll look at alternative HoT configuration options in the meantime.

6

@blake.gilchrist

Thank you for your patience. Please let me know if there’s anything I can help you with.