-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Tree: Impossible to get tree node's element (data-id attribute absent) #15020
Comments
PR opened with the lost attribute #15021 |
Thanks for this! I can confirm it is still causing problems for us and we have been unable to migrate to Prime v17, as it breaks a lot of our Automation tests, which is very important to the stability of our application. |
Fixed in #15021 until the PassThrough arrives. You'll be able to pass any attribute you want with PassThrough which is in implementation progress right now. |
This issue is fixed in 17.11.0, closing the issue and update the milestone. |
Describe the bug
Hello PrimeNG team,
Tree component lost its attribute data-id on each tree node element. It's really embarassing because we cannot tell to a third party library that it have to be plugged on a given node's HTML element... (like popover, etc...)
This attribute was lost here : 12d79f7
An existing issue corresponding to this bug was closed by error (I suppose, because this bug is still present in code) : #14541
A PR was also opened by @adyeardley to correct this issue : #14552
Also, your function focusVirtualNode (
primeng/src/app/components/tree/tree.ts
Line 701 in fd18d96
Can you please reopen this little PR and merge it please? Or just add again this attribute on node's element.
Thanks in advance and have a nice day.
Environment
Angular 17 application
Reproducer
No response
Angular version
17.2.2
PrimeNG version
17.10.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.11.1
Browser(s)
Chrome 122
Steps to reproduce the behavior
Expected behavior
Each node's element have to got a data-id attribute corresponding to its key property.
The text was updated successfully, but these errors were encountered: