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

Context Menu in nested content incorrectly placed #13936

Closed
hugograf opened this issue Oct 22, 2023 · 1 comment
Closed

Context Menu in nested content incorrectly placed #13936

hugograf opened this issue Oct 22, 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

@hugograf
Copy link
Contributor

Describe the bug

In nested content, the context menu is displayed too far down and too far to the right. This bug was already noticed in issue #3572. Until version 16.0.2 the problem could be worked around with appendTo="body". But since version 16.1.0 the context menu is not closed correctly with appendTo="body". It remains visible beyond the existing context.

Environment

PrimeNG 16.5.1 but since 16.1.0

Reproducer

https://stackblitz.com/edit/fpv3rx?file=src%2Fapp%2Fdemo%2Ftable-row-expand-demo.ts

Angular version

16.X

PrimeNG version

16.5.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.16.0

Browser(s)

No response

Steps to reproduce the behavior

See video: https://youtu.be/7YgWlCv9Z2U

Expected behavior

Either the context menu is displayed correctly in nested content without appendTo="body" or the context menu is closed correctly when the content is destroyed.

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