On searching a term in the search pop up , the screen doesn't take to the value found

When searching for a term using the search popup, the screen does not navigate to the matched value. I tested this on the Aspose.Cells demo site. If the file contains a large amount of data, the search result is found but the view does not scroll to that location."

@sarathepiq

It appears you are encountering an issue with the search functionality on the Aspose.Cells demo site, where the view does not automatically scroll to the matched value when searching within a large dataset. This behavior may be related to how the search results are managed in the user interface.

To address this issue, consider the following workarounds:

  1. Manual Scrolling: After executing the search, manually scroll to the location of the found value.
  2. Programmatic Scrolling: If you have access to the underlying code, you can implement a feature that programmatically scrolls to the found cell after the search is completed.

For further assistance, it may be helpful to check the Aspose.Cells documentation or the support forum for any updates or similar issues reported by other users.

@sarathepiq
Would you like to provide your sample file? If you could take a screenshot and highlight the error, it would be very helpful for us to locate the issue. We will check it soon.

image.png (96.2 KB)

Book1.zip (20.0 KB)

I attached the file and screenshot. When I search for the value ‘4000’, the control does not navigate to the corresponding cell. This issue was observed during testing on the Aspose.Cells demo site.

@sarathepiq
Thanks, we can reproduce this 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-1931

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 Peter, Is this planned along with upcoming V25.10

@purushothamj
Yes. The fix will be included in the next version 25.10 which will be released in the first half of October.