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

Update of MenuItem's 'expanded' property not working #14329

Closed
marcioluish opened this issue Dec 11, 2023 · 0 comments
Closed

Update of MenuItem's 'expanded' property not working #14329

marcioluish opened this issue Dec 11, 2023 · 0 comments
Assignees
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Milestone

Comments

@marcioluish
Copy link

marcioluish commented Dec 11, 2023

Describe the bug

This Stackblitz link was forked from PrimeNG 16.9.1 Multiple PanelMenu.

In that, a button was added to change Edit and Archieve submenus as the following:

  • Labels = 'Sub Item Title'
  • expanded = false

However this isn't working, at least compared to PrimeNg version 16.0.2, which you can find a Stackblitz link here (just changed PrimeNg version in package.json)

Steps to replicate issue at Stackblitz (both of two links above):

  1. Expand Events menu
  2. Expand both Edit and Archieve submenus
  3. Click on Change button
  4. Expected: both Edit and Archieve submenus labels changed to Sub Item Text and both collapsed

Before:
image

After:
image

I've noticed this, because we recently upgraded Angular and PrimeNg versions to ~16.3.0 in our project, and we had methods to handle expansion/collapse (mostly mngt of 'expanded'property) of 3rd and 4th menu levels, which were working fine in v15 & v16.0.2.

I don't know if in PrimeNG versions greather than 16.0.2, expansion was supposed to be handled differently, bc I couldn't find anything related.

I'd really appreciate if anyone could provide some support in this matter.

Cheers.

Environment

Angular 16.2.1 so as PrimeNg 16.3.1

Reproducer

No response

Angular version

16.2.1

PrimeNG version

16.3.1

Build / Runtime

Angular CLI App

Language

TypeScript

Node version (for AoT issues node --version)

20.5.0

Browser(s)

No response

Steps to reproduce the behavior

No response

Expected behavior

No response

@marcioluish marcioluish added the Status: Needs Triage Issue will be reviewed by Core Team and a relevant label will be added as soon as possible label Dec 11, 2023
@cetincakiroglu cetincakiroglu added Type: Bug Issue contains a bug related to a specific component. Something about the component is not working 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 13, 2023
@cetincakiroglu cetincakiroglu added this to the 17.1.0 milestone Dec 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Issue contains a bug related to a specific component. Something about the component is not working
Projects
None yet
Development

No branches or pull requests

3 participants