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

Component: panelMenu bugs dropdown in sidepanel after reopening #13951

Closed
HackingLutz opened this issue Oct 24, 2023 · 4 comments
Closed

Component: panelMenu bugs dropdown in sidepanel after reopening #13951

HackingLutz opened this issue Oct 24, 2023 · 4 comments
Labels
Resolution: Cannot Replicate Issue could not be replicated by Core Team Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response

Comments

@HackingLutz
Copy link

HackingLutz commented Oct 24, 2023

Describe the bug

In out application we use the PanelMenu inside a SidePanel Component as our Usermenu. If you open the SidePanel right after initial loading of the page you are on and choose to open a Menuitem inside a dropdown of the PanelMenu it loads just fine, but after closing the sidepanel and open the dropdown item again there is a visual bug.

image

Environment

Running node locally on my computer and use Angular / Primeng. The identified problem is only within PrimeNg/Angular.

Reproducer

No response

Angular version

16.2.7

PrimeNG version

16.5.2

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

v18.3.0

Browser(s)

Chrome, Firefox, Safari, Edge

Steps to reproduce the behavior

  1. Refresh site (CTRL+F5)
  2. Open sidebar
  3. Expand "Clean up"
  4. Collapse "Clean up"
  5. Close sidebar
  6. Open sidebar
  7. Expand "Clean up"

Expected behavior

No response

@HackingLutz HackingLutz 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 24, 2023
@jermylucas
Copy link
Contributor

I had a similar issue once but it's extremely difficult to diagnose without a reproducible product. Can you provide it?
Does your p-panelMenu have the [multiple]="true" set?

@cetincakiroglu cetincakiroglu added Resolution: Cannot Replicate Issue could not be replicated by Core Team and removed Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible labels Dec 27, 2023
Copy link

We're unable to replicate your issue, if you are able to create a reproducer by using PrimeNG Issue Template or add details please edit this issue. This issue will be closed if no activities in 20 days.

Copy link

This issue has been automatically marked as stale. If this issue is still affecting you with the latest version, please leave any comment, and we will keep it open. We are sorry that we have not been able to prioritize it yet. If you have any new additional information, please include it with 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 Apr 26, 2024
Copy link

github-actions bot commented May 3, 2024

Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you for your understanding!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution: Cannot Replicate Issue could not be replicated by Core Team Resolution: Stale Issue or pull request is inactivity and unfortunately it will be *closed* if there is no response
Projects
None yet
Development

No branches or pull requests

3 participants