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
Describe the bug
When navigating between pages using Angular's routerLink, the dropdown components powered by Flowbite do not initialize correctly on the new page unless a full browser reload is performed. This issue affects navigation from a login page to an admin page, both of which utilize Flowbite's dropdown component.
To Reproduce
Start the Angular application with Flowbite dropdown components on the login and admin pages.
Navigate from the login page to the admin page using routerLink.
Observe that the dropdown on the admin page does not function.
Reload the browser on the admin page; the dropdown now works as expected.
Expected behavior
The dropdown components should initialize and function correctly after navigation between pages without requiring a browser reload.
Desktop (please complete the following information):
OS: MacOS
Browser: Google Chrome
Version: 123.0.6312.122
Additional context
Currently, I am initializing Flowbite on every NavigationEnd event by subscribing to router events in the ngOnInit lifecycle hook of the app.component.ts.
Alternatively, a directive is used specifically on components where Flowbite is utilized to manage the initialization, ensuring that elements are properly recognized and initialized by Flowbite post-navigation. (source)
Describe the bug
When navigating between pages using Angular's
routerLink
, the dropdown components powered by Flowbite do not initialize correctly on the new page unless a full browser reload is performed. This issue affects navigation from a login page to an admin page, both of which utilize Flowbite's dropdown component.To Reproduce
Reload the browser on the admin page; the dropdown now works as expected.
Expected behavior
The dropdown components should initialize and function correctly after navigation between pages without requiring a browser reload.
Desktop (please complete the following information):
Additional context
Currently, I am initializing Flowbite on every
NavigationEnd
event by subscribing to router events in thengOnInit
lifecycle hook of the app.component.ts.Alternatively, a directive is used specifically on components where Flowbite is utilized to manage the initialization, ensuring that elements are properly recognized and initialized by Flowbite post-navigation. (source)
The text was updated successfully, but these errors were encountered: