-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
MenuItem: Update of 'expanded' and 'label' properties not working #14893
Comments
Fixed #14893 - PanelMenu | Refactor to trigger change detection in su…
I attempted to update PrimeNG to 17.11 and it caused a major regression in behavior of the When expanding a node, it seems to briefly expand all of the children under that node before immediately collapsing them. When you go to collapse the parent, the same process occurs, where it expands and then collapses the children before collapsing the parent. I backed it down again to 17.8 and everything is working as normal. We aren't doing anything fancy with the menu as far as I can tell. We set the
That's about it. But it was unusable in 17.11. I don't know if this is the specific commit that is causing us problems, but it does deal with |
@cetincakiroglu the chagen/fix is not working for me as well. Stackblitz Link |
Hi @cetincakiroglu, thanks for looking into it. |
Hi, Re-opened and transferred in v17.12.0 milestone. |
Hi, Thanks for the feedback, I've found that there is a missing condition in the if statement in line 131 of panelMenuSub component which causes the issue of child expansion on root list item click. Rendering issue is fixed for good. Could you please test it after the release? |
Hi @cetincakiroglu thanks for checking this out. Yes, I'll try it as soon fix is released. |
Hi @cetincakiroglu 17.12 still fails to manage And below is the modified stackblitz link of 17.12 PanelMenu's Multiple. Please have a look at it again to see if anything is wrong when trying to set those MenuItem's properties. Desirable behavior would be the same that we had in 16.0.2 (first GIF of this card) Thanks again. |
Hi, I guess the problem is that the change detection is not triggered. I can make it work a little bit refactoring https://stackblitz.com/edit/sg4yxy-rnqdjm?file=package.json,src%2Fapp%2Fdemo%2Fpanel-menu-multiple-demo.ts |
@cetincakiroglu thanks for the response. |
Also @cetincakiroglu, I noticed that when manipulating Is this something that can be prevented without explicitly using html manipulation? |
Hi, thanks for letting us know. We'll check the issue again before the 17.14.0 release. |
Hello, Is there any update on this? I'm seeing this issue in my app and we're on 17.18.11. The demo on your website seems to be on the same version and has the same issue: https://primeng.org/panelmenu#controlled To repro at that link:
Thanks in advance! |
Describe the bug
The following issue was opened in 12/11/2023 and closed in 12/13/2023, having the fix being checked in v17.1.0.
#14329
I honestly didn't follow up PanelMenu's new releases, but in v17.1.0 the issue was only partially fixed and now in v17.8.0, we have the same behavior as in versions above v16.0.2.
Below you can find 2 GIFs comparing v16.0.2 and v17.8.0. In these I access sub-menu items and change their
label
andexpanded
properties by clicking in theChange
button.Here's the link to Stackblitz using v16.0.2: https://stackblitz.com/edit/gegncb?embed=1&file=package.json
v16.0.2
v17.8.0
Environment
Angular 17.2.1 so as PrimeNg 17.8.0
Reproducer
https://stackblitz.com/edit/4sbrb2-gkf3lq?file=src%2Fapp%2Fdemo%2Fpanel-menu-multiple-demo.ts
Angular version
17.2.1
PrimeNG version
17.8.0
Build / Runtime
Angular CLI App
Language
TypeScript
Node version (for AoT issues node --version)
20.10.0
Browser(s)
No response
Steps to reproduce the behavior
No response
Expected behavior
No response
The text was updated successfully, but these errors were encountered: