You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
bug: wrapped menu does not work with content property #16304
1 - Generate a new app with menu
2 - Put the ion-menu in the app-menu <ion-menu contentId="content1" > <ion-header> <ion-toolbar> <ion-title>Menu</ion-title> </ion-toolbar> </ion-header> <ion-content> <ion-list> <ion-menu-toggle auto-hide="false" *ngFor="let p of appPages"> <ion-item [routerDirection]="'root'" [routerLink]="[p.url]"> <ion-icon slot="start" [name]="p.icon"></ion-icon> <ion-label> {{p.title}} </ion-label> </ion-item> </ion-menu-toggle> </ion-list> </ion-content> </ion-menu>
3 - Put the following in app.component: <ion-app> <ion-split-pane> <app-layout-menu contentId="content1" [content1]="content"></app-layout-menu> <ion-router-outlet id="content1" main [swipeBackEnabled]="true"></ion-router-outlet> </ion-split-pane> </ion-app>ion
It's too bad that the functionality has changed since v3. With a v3 project it was straight forward to have ion-menu components on multiple pages/components of the application. This provided more flexibility with the contents of the menu, as well as functionality. It seems that the new implementation of this component intends for ion-menu to only be used for routing.
I agree with @iTEEECH, I find the way that this component has been designed to be poor. The implementation for v3 provided far more flexibility
Any update on this? I'm on v5 and I get this error in production but not in development mode. On debugging found that it happens with SSR. So might be related to this issue stenciljs/core#2119
And as mentioned there having same content-id removes the error but my menu behaves strangely with no menu visible at all
changed the title [-]bug(v4-menu): Menu: must have a "content" element to listen for drag events on. [/-][+]bug: wrapped menu does not work with content property[/+]on Jul 26, 2022
Thanks for the issue. This has been resolved via #28801, and a fix will be available in an upcoming release of Ionic Framework. We are shipping this in a major release of Ionic to de-risk some of the internal infrastructure changes we made to resolve this bug. Feel free to continue testing the dev build, and let me know if you run into any issues.
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.
Activity
iTEEECH commentedon Nov 28, 2018
Hi
Nobody has any solution for this bug ?
thank you so much !
paulstelzer commentedon Dec 7, 2018
Thanks for your issue! That seems to be like a bug. A workaround would be this:
iTEEECH commentedon Dec 10, 2018
Thank you for your answer ! So it is impossible to apply the principle of angular and to cut the components ?
paulstelzer commentedon Dec 10, 2018
Okay, sry. I've updated my answer above. It's a bug, you are right :)
iTEEECH commentedon Dec 11, 2018
No problem, I will look in my side If I have the time and wait the next version to test :)
8 remaining items
liquidcms commentedon Jun 12, 2019
Hmm.. i had MenuController imported on one of my pages; this may have been breaking it.
speence commentedon Jul 15, 2019
It's too bad that the functionality has changed since v3. With a v3 project it was straight forward to have ion-menu components on multiple pages/components of the application. This provided more flexibility with the contents of the menu, as well as functionality. It seems that the new implementation of this component intends for ion-menu to only be used for routing.
I agree with @iTEEECH, I find the way that this component has been designed to be poor. The implementation for v3 provided far more flexibility
ishan123456789 commentedon Jun 6, 2021
Any update on this? I'm on v5 and I get this error in production but not in development mode. On debugging found that it happens with SSR. So might be related to this issue stenciljs/core#2119
And as mentioned there having same
content-idremoves the error but my menu behaves strangely with no menu visible at allKANekT commentedon Apr 8, 2022
bug is actual with #24907
[-]bug(v4-menu): Menu: must have a "content" element to listen for drag events on. [/-][+]bug: wrapped menu does not work with content property[/+]liamdebeasi commentedon Jan 10, 2024
Hi everyone,
Here is a dev build if anyone is interested in testing a proposed fix:
7.6.2-dev.11704922151.1fd3369fInstall example:
Please note that this is an Ionic 8 build and is subject to the Ionic 8 breaking changes.
fix(menu): menu can be encapsulated in a component (#28801)
liamdebeasi commentedon Jan 15, 2024
Thanks for the issue. This has been resolved via #28801, and a fix will be available in an upcoming release of Ionic Framework. We are shipping this in a major release of Ionic to de-risk some of the internal infrastructure changes we made to resolve this bug. Feel free to continue testing the dev build, and let me know if you run into any issues.
ionitron-bot commentedon Feb 14, 2024
Thanks for the issue! This issue is being locked to prevent comments that are not relevant to the original issue. If this is still an issue with the latest version of Ionic, please create a new issue and ensure the template is fully filled out.