Skip to content
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

OrganizationChart: Expanding the tree data with additional child nodes results in a visual glitch #13913

Closed
pistage opened this issue Oct 18, 2023 · 1 comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible

Comments

@pistage
Copy link
Contributor

pistage commented Oct 18, 2023

Describe the bug

Fewer children
Skärmavbild 2023-10-18 kl  12 35 36

More children
Skärmavbild 2023-10-18 kl  12 35 21

Environment

Tested on a local computer and Stackblitz with the same result.

Reproducer

https://stackblitz.com/edit/github-tsea2s?file=src%2Fapp%2Fapp.component.ts

Angular version

16.2.9

PrimeNG version

16.5.0

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

Unknown

Browser(s)

No response

Steps to reproduce the behavior

In the provided Stackblitz link, you can in the app.component.ts file remove the elements enclosed by the comments marked as "Begin" and "End". Upon doing so, you can observe that the organizational chart displays an unusual adjustment in the lines leading to the top node. Upon further investigation, it becomes evident that adding additional items (children) progressively displaces the line connecting to the top node from its intended position.

Expected behavior

The line going to the top node should be aligned correctly where the box of the node is located.

@pistage pistage added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Oct 18, 2023
Copy link

This issue has been automatically marked as stale due to a lack of activity. If this issue is still relevant to you, please leave a comment so we can keep it open. We apologize for not being able to prioritize it sooner. If you have any new information or questions, please share them in your comment!

@github-actions github-actions bot added the Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible
Projects
None yet
Development

No branches or pull requests

2 participants