Resolved issue 10963 in panel menu

[NilavPatel]

Fixes #10963
Fixes #12173

[NilavPatel]

Solution for defect
#10963

[rodolfocipagauta]

Sigo esperando la solución para este defecto.
Por el momento reemplace ese componente por el SLIDEMENU, por si a alguien le sirve como solución temporal.
Gracias.

[ColinNor]

Hi @NilavPatel will this problem be fixed in the near future?

[NilavPatel]

Not sure, I have created pull request with solution, but no one has review and merge it.

[Zagano-AOR]

Do you have any news on this one?... for us, this issue will define a go/no go with the latest version or keep PrimeNG version 9... the bad thing is that we bought the theme designer to do the migration, and now we are very disappointed since we have lots of panel menus inside sidebars :( !!

[NilavPatel]

@yigitfindikli would you please take a look at this merge request? Lots of peoples are facing this issue now.

[ColinNor]

I sent a mail to support and was told that this issue will be fixed in the next release

[Zagano-AOR]

Really, excellent news... I just can't wait

[AlexAvilaSantos]

<p-sidebar [(visible)]="visibleSidebar"  >
    <p-panelMenu *ngIf="visibleSidebar" [model]="modulos" autoDisplay="true"></p-panelMenu>
</p-sidebar>[](url)

lil trick, use same boolean for visible with ngif in panelMenu, have visual bug but works

[cetincakiroglu]

Hi @NilavPatel,

Thanks a lot for your first-time contribution!
Don't forget to run npm run build:check command before pushing changes.