Topic: Sidenav not toggling on Chrome variants, works on Firefox
Expected behavior
I'm using a navbar menu item, an A, to toggle a sidenav. The sidenav configuration is: right=true, mode=over.
Actual behavior
On Firefox (latest, 110.0.1), it works as expected: I click the toggle A, the sidenav shows up from the right, everything else gets dimmed by the overlay.
On Vivaldi (5.7.2921.60), Chrome ( 111.0.5563.64), Chromium (111.0.5563.64) -- they are all recent versions, something else happens.
If the page has NO scrollbar, just a bit of content, it works as expected.
However, if the page has a scrollbar, the window gets dim for a fraction of a second as if the overlay would activate, but then nothing happens and in the console I find this:
"perfect-scrollbar.esm.js:114 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952"
Resources (screenshots, code snippets etc.)
Everything works correctly if the sidenav is on the left, on all browsers, regardless of scrollbar presence.
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Opened
- User: Priority
- Premium support: Yes
- Technology: MDB Standard
- MDB Version: MDB5 6.2.0
- Device: Laptop
- Browser: Chrome, Chromium, Vivaldi, Firefox
- OS: Linux
- Provided sample code: No
- Provided link: Yes
mlazaru staff commented 2 weeks ago
Thank you for reporting this bug. We will fix it soon.
octavian.gherghinis priority commented 2 weeks ago
Hello. I need to set my expectations, can you give me an idea of what "soon" means ? Days, weeks ?
kpienkowska staff commented 2 weeks ago
We do not disclose when the next release is to be or what it will contain.
octavian.gherghinis priority commented 1 week ago
Great. Then can I please have a workaround for this issue ?
mlazaru staff commented 1 week ago
I'm afraid we can't make a good workaround solution for that issue without changing source code. Please stay patient and follow our changelog.