[GH #2151] Column widths incorrect with nestedHeaders plugin

Questions
,
1

I am using nested headers and I’m trying to set the column widths of my columns. I have set up a simple fiddle that demonstrates the problem: Handsontable Nested Headers column widths - JSFiddle - Code Playground

I want each of my columns to be 40px, yet the column widths vary widely once I use nested headers.

Can you help?

Thanks,
David

nestedHeaders interfere column width setting
2

Hi @dhaber

I checked with our example in the documentation and it works correctly, even with just one level of rows: https://jsfiddle.net/qr8fpkma/1/

If you are planning to only have one level the better idea would be to use the colHeaders option and set the custom names in the array of arrrays.

3

Your example works because your column name is a single letter (i.e. it is narrower than the width you’re trying to set). If your column name was wider, as in my example, it would not work.

4

@dhaber

You are right. I did some more research and find that this is actually a regression to version 12.1. We have it already reported, so I will add your case and update you once the fix is done.

5

Great. Thank you very much @adrian.szymanski!

6

@dhaber,
let me know if this works in the interim:

.htCore colgroup col {
  width: 40px !important;
}
7

My column configuration has many more columns than my sample that illustrates the bug for the HoT folks, so your solution won’t work in practice. Thanks anyway.

8

Hey @adrian.szymanski. It appears my fix is not in 15.2.0. Can you give me some sense of when it might be done?
Thanks,
David

9

Hi @dhaber

That’s correct, this issue hasn’t been fixed yet. I’ll update you as soon as it’s done.

10

Hi @adrian.szymanski, can you give me some idea when I can expect this to be fixed? I’m holding up a feature that really needs to get out during the summer.
Thanks.

11

Hi @dhaber

It’s not on our roadmap yet. I’ll let you know when the fix is ready.

12

Considering it’s a regression bug, that’s kind of disappointing.

@aleksandra_budnik is there anything we can do to get it prioritized?

13

Hi @dhaber

Actually, I was the one who reported the need to check the behavior some while ago. Documentation does not clearly say what is the expected outcome so we cannot report it as a regression.

@adrian.szymanski already raised the priority of the issue in our internal system. I hope that we will be able to share some more feedback soon.

1 Like
14

Hi @dhaber , I am happy to report that this issue has been resolved with the release of v17.0.1 this morning. Thanks again for reporting the issue, and please let us know if you continue to experience any similar problems in the latest release.

15

Hello, If your column name was wider, as in my example, it would not work.

16

Thank you @joseph.petty. Major version upgrades (with the associated breaking changes) take some time for us to get to. I will update here as soon as I can test it.