Error while setting showHeaders to false and using .setRowHeight method

Dear Syncfusion Team,

I am facing an issue where, when setting and using the .setRowHeightmethod in the typescript component, I get an error saying "Error: Cannot read property 'getElementsByClassName' of undefined"

I faced a similar issuehereand was told it would be fixed on January 12th 2021. Would you please kindly have a closer look and provide an update regarding this issue?
In the meantime, I simply hid both headers with some simple CSS styling :
.e-spreadsheet .e-row-header,
.e-spreadsheet .e-header-panel {
display: none !important;
}
.e-spreadsheet .e-main-panel .e-sheet-content {
width: 100% !important;
}
Thank you,
Remy

3 Replies 1 reply marked as answer

SP Sangeetha Priya Murugan Syncfusion Team February 8, 2021 12:23 PM UTC

Hi Remy, 
 
Thank you for contacting Syncfusion support. 
 
We have checked your reported reported issue and we would like to let you know that the setRowHeight method works properly in our end. In your sample also the issue not replicated in the version (18.4.41) and the CSS customization also not available. So, please share the exact case for issue replicating scenario. Based on that we will check and provide you a better solution quickly. 
 
Regards, 
Sangeetha M 



RE Remy February 9, 2021 01:40 AM UTC

Hi Sangeetha,

I am not quite sure I understand. Do you not experience the same issue on your end? It might not be the setRowHeight property, but there definitely seems as though something breaks the app as soon as the showHeaders parameter is set to false. As a workaround, the styling I used to hide the headers in my actual project is the following :

/* Hide headers */
.e-spreadsheet .e-row-header, .e-spreadsheet .e-header-panel { display: none !important; }
.e-spreadsheet .e-main-panel .e-sheet-content { width: 100% !important; }

 Here is a link to the sample project and a video demonstration :





Thank you,
Remy


SP Sangeetha Priya Murugan Syncfusion Team February 9, 2021 12:16 PM UTC

 
Hi Remy, 
 
Thank you for your update. 
 
We have already fixed your reported issue in our latest patch release (18.4.42). So, we would suggest you to use the latest version to resolve this issue in your end. 
 
 
Regards, 
Sangeetha M 


Marked as answer
Loader.
Up arrow icon