-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
clr-dg-detail not working with server-driven data grid #1704
Comments
Hello, Looks like the link for reproduction that you left is not pointing to the right place. Could you check it out and give proper reproduction link? |
I used a link from the clarity documentation about the server-driven data grid. and added this code also from the documentation:
changing Shortly: i can see '>>' but nothing happens when i click on it. |
Please share link to the StackBlitz you created. |
Detail pane requires 'clrDgItem' to be used on the rows as that is the context used for it. Please check the examples on the page |
The clr-dg-detail component does not function as expected when used with a server-driven data grid. When attempting to display detail rows, the component fails to load or display the additional data properly, causing an inconsistent or broken UI behavior.
How to reproduce
Add clr-dg-detail to the grid in the provided StackBlitz example: StackBlitz Reproduction Link.
Attempt to expand a detail row in the data grid.
Observe that the detailed information does not expended.
Expected behavior
The clr-dg-detail component should expand a row, regardless of whether the data is server-driven or client-side.
Versions
Clarity version: v17.x
Framework version: Angular 18
Device:
Type: MacBook Pro
OS: macOS 13.2
Browser: Chrome
Version: 109
Additional notes
This issue only occurs when the data grid is connected to a server-driven data source. It functions as expected when using a static data set. This may be related to how the data is fetched or rendered in the detail row.
The text was updated successfully, but these errors were encountered: