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

OverlayPanel: Wrong positioning on first open #13813

Closed
Gykonik opened this issue Oct 5, 2023 · 1 comment
Closed

OverlayPanel: Wrong positioning on first open #13813

Gykonik opened this issue Oct 5, 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

@Gykonik
Copy link

Gykonik commented Oct 5, 2023

Describe the bug

I'm using a button to trigger an OverlayPanel in the bottom right corner of a card. When the panel opens up for the first time, the position is wrong and it overflows. However, when I close and re-open it, everything works. Is there anything I'm missing, or is this a bug in the positioning logic?

Initial positioning:
image

After closing and opening the popup again, the result is as expected:
image

Environment

Windows 11, Chrome (bot doesn't work on any environment I've tested)

Reproducer

https://stackblitz.com/edit/bqzap2?file=src%2Fapp%2Fdemo%2Foverlay-panel-target-demo.html

Angular version

16.2.0

PrimeNG version

16.4.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

18.18.0

Browser(s)

all

Steps to reproduce the behavior

Just click on the information icon and see that it overflows. When closing the popup and re-open it, it has the proper positioning.

Expected behavior

No response

@Gykonik Gykonik 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 5, 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