I'm currently using the Flowbite navbar from https://flowbite.com/docs/components/navbar/ into my project. While the navbar functions correctly on desktop, however I've encountered an issue on mobile devices: the hamburger menu fails to appear when clicked. This behavior is unexpected and disrupts the intended responsive design of the navbar.
To provide context, my project is built using the latest version of Next.js (v15). I've followed the integration steps outlined in Flowbite's documentation to implement the navbar component. The desktop view displays the navbar with all functionalities, including dropdowns and links, working as expected. However, when switching to mobile view, clicking the hamburger icon, which is supposed to toggle the menu visibility, does not yield any visible changes.
Could you please advise on potential reasons for this behavior and any troubleshooting steps I could undertake? Your insights would be greatly appreciated to resolve this mobile display issue effectively.
I tried it with React Js, and it worked fine. However, it seems there's an issue with Flowbite UI in Next.js version 15. Hopefully, the developers will notice and fix this problem as soon as possible. Thanks!
I'm currently using the Flowbite navbar from https://flowbite.com/docs/components/navbar/ into my project. While the navbar functions correctly on desktop, however I've encountered an issue on mobile devices: the hamburger menu fails to appear when clicked. This behavior is unexpected and disrupts the intended responsive design of the navbar.
To provide context, my project is built using the latest version of Next.js (v15). I've followed the integration steps outlined in Flowbite's documentation to implement the navbar component. The desktop view displays the navbar with all functionalities, including dropdowns and links, working as expected. However, when switching to mobile view, clicking the hamburger icon, which is supposed to toggle the menu visibility, does not yield any visible changes.
Could you please advise on potential reasons for this behavior and any troubleshooting steps I could undertake? Your insights would be greatly appreciated to resolve this mobile display issue effectively.