❗ “Add Row” and “Add Column” Actions Insert in Incorrect Location in Aspose GridJS & Unfreeze Cell Not Reflected in Saved Copy After JSON Merge in Aspose GridJS

@chirags,

I tested it using the online Excel editor (created by Aspose.Cells.GridJs) and found, in the generated Excel file, the hyperlinks/links are not retained.

We require thorough evaluation of the issue. We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSGRIDJS-1852

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

Hi Team,

I noticed a difference in behavior when handling cell updates via the cells-updated event.

Here’s my code:

xs.on('cells-updated', (name, cells) => {                      
    cells.forEach((acell, index, array) => {
        console.log('acell got updated:', acell);
        // acell.text shows current cell value
    });
});

:test_tube: Behavior Observed:

  • When I click Format Cell (e.g., set number format), the value in acell.text does not change immediately.
  • But when I click Percentage format, acell.text shows the updated value directly.

:pushpin: Request:

Could you please check why the behavior is inconsistent between different format options (general/number vs percentage)?
I’ve attached a screenshot showing this difference for reference.

image.png (448 Bytes)
image.png (1.6 KB)
image.png (10.1 KB)

Percentage format
image.png (448 Bytes)
image.png (1.1 KB)
image.png (10.4 KB)

Thanks for your support.

@chirags
Hello, I’ve observed that adjusting the number format options in Format Cell triggers a real-time update of the cell value, thus firing the cells-updated event. I have created a ticket to optimize this.

We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSGRIDJS-1864

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

The issues you have found earlier (filed as CELLSGRIDJS-1864,CELLSGRIDJS-1852) have been fixed in this update. This message was posted using Bugs notification tool by leoluo

@chirags
Those issues have been fixed in v25.9. Please have a try.
You shall update serverside to the latest v25.9 version in nuget package.
and the client js to the latest v25.9 version also.

Thank you for the update. We found another issue:

When we load a file and go to the Review tab, clicking on Edit Comment spoils the UI layout.

Steps to reproduce:

  1. Load any file in GridJs.

  2. Do not make any changes.

  3. Go directly to the Review tab.

  4. Click on Edit Comment.

  5. The UI gets spoiled (please check the attached screenshot for reference).

image.png (71.4 KB)
image.png (25.0 KB)

Could you please verify this behavior and confirm if it’s a bug or if there is a specific way to handle the edit option under the Review menu?

Thank you for your support.

@chirags
we cannot reproduce this issue.
by running the latest demo in

or

or in our live app

can you provide your sample project?

I also tried the same steps in your online demo, and the issue is happening there as well.

Steps followed:

  1. Opened your online demo.

  2. Loaded a file.

  3. Without making any changes, went to the Review tab.

  4. Clicked Edit Comment.

  5. The UI layout was spoiled (screenshot attached).

    image.png (37.4 KB)

This confirms that the issue is not specific to my environment but also reproducible in your demo. Could you please check and fix this?

Thank you.

@chirags,

I am sorry but still I could not reproduce the issue using the online editor app created by latest version of Aspose.Cells.GridJs. I simply load an Excel file into it and do as you directed, it works fine and the UI does not get spoiled.

@chirags
Furthermore, we also tried using Firefox and Edge, but we still couldn’t reproduce this issue. Could you please record a screen video to demonstrate the problem?

This seems to be a file-specific issue, because it works properly with other files.

However, I also found another problem: when I export as PDF, the output is not correct. Some columns are being cut off and moved to the next page instead of fitting properly on the same page.

image.png (41.0 KB)

Could you please check this behavior as well?

Thank you.

@chirags,

Please zip and attach the template Excel file and output PDF by Aspose.Cells for .NET. We will check your issue soon.

I am sending you the attached file in which I am facing the issue.

Steps to reproduce:

  1. Preview the file.

  2. Change the sheet and go to Sheet1.

  3. Open the Review tab and click on Edit Comment → the UI gets spoiled.

  4. Also, try to export this file as PDF → the output is not correct, some columns are cut off and moved to the next page.

chart.zip (37.1 KB)

This issue happens specifically with this file. Could you please check?

Thank you.

@chirags
Using the file you provided.We can reproduce the first issue.
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue  : CELLSGRIDJS-1943  Edit comment does not work as expected

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

@chirags,

Thanks for the sample Excel file.

I tested your scenario using an online editor app and observed the issue. The problem arises due to the large merged cell A1 (spanning the range A1:L1). When selecting the “Edit Comment” option from the Review menu, the UI popup appears at the top-right boundary of the worksheet. However, clicking on any other cell, such as A2 (then using “Edit Comment” option), resolves the issue. We will investigate this further. A ticket with the ID “CELLSGRIDJS-1943” has been logged, and we will address it promptly.

I tested your Excel file and found that this is not an issue with the component. The Aspose.Cells.GridJs tool, which functions similarly to MS Excel, generates PDF files based on the print previews of the worksheet. To verify this, you can manually open the Excel file in MS Excel and navigate to Sheet1. Then, check the Print Preview of the worksheet, and you will notice that the display matches the output PDF generated by Aspose.Cells. Additionally, if you save the file as a PDF directly in MS Excel, you will achieve the same results.

1 Like

In MS Excel, we have the option “Fit all columns on one page” while exporting to PDF, so we can manage this issue there. Is there something similar available in GridJs to handle this?

image.png (101.1 KB)

Thank you.

@chirags,

Thanks for the screenshot.

We have these options available in Aspose.Cells library. So you may use them when rendering Excel file to PDF via Aspose.Cells. See the documents with examples for your reference.

I know this feature is available in Aspose.Cells where we can set the option to fit all columns on one page while exporting to PDF.

But what about Aspose.Cells.GridJs?

When I click Download As PDF from the File menu in GridJs, how can I change that behavior so it uses the same “Fit All Columns on One Page” option? Can you please guide me on how to configure this?

Thankyou

@chirags
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue  : CELLSGRIDJS-1944  Support option "Fit all columns on one page" while exporting to PDF in GridJs

You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.

In the earlier version, when I added or edited a comment it was saving automatically on the server side — I didn’t have to do a manual save.

But in the new version, the comment auto-save is not working anymore. Now I have to save it manually for it to persist on the server side. Can you please check this?

thankyou