Topic: mdbStickyHeader disappearing on iOS Safari
raichshlv free asked 3 years ago
Expected behavior When scrolling to the top, navbar is visible. Actual behavior Navbar is visible while actually scrolling to the top, but just as it stops at the very top, the navbar goes away as if scrolled down. Resources (screenshots, code snippets etc.) This also happens on your demo at https://ng-demo.mdbootstrap.com/navigation/sticky-header
FREE CONSULTATION
Hire our experts to build a dedicated project. We'll analyze your business requirements, for free.
Status
Answered
Specification of the issue
- ForumUser: Free
- Premium support: No
- Technology: MDB Angular
- MDB Version: 10.0.1
- Device: iPad, iPhone
- Browser: Safari
- OS: iOS
- Provided sample code: No
- Provided link: Yes
Arkadiusz Idzikowski staff commented 3 years ago
Thank you for letting us know about this problem, we will take a closer look at that.
Which version of the Safari browser do you use?
raichshlv free commented 3 years ago
I was running iOS 14.2 and whichever latest version is currently available for it. The same issue also happened on an old iPad 2 running iOS 9. I guess the Safari animation, which triggers page reload, when pulling the page down, causes the navbar to disappear.
raichshlv free commented 3 years ago
Have you checked this out? Any ETA on a fix?
Arkadiusz Idzikowski staff commented 3 years ago
@raichshlv We managed to reproduce this bug on our end, but we still need to find the cause of the problem and we can't provide an ETA yet.
jasper heeren free commented 3 years ago
Having the same problem, any workaround available till a fix will be published?
Arkadiusz Idzikowski staff commented 3 years ago
@jasper heeren Unfortunately, we can't provide a workaround, because we didn't find the cause of the problem yet.
jasper heeren free commented 3 years ago
Any updates on this?
rhaouari free commented 3 years ago
having the same issue with safari on Mojave
Arkadiusz Idzikowski staff commented 3 years ago
We are still working on this issue. We will update the thread when the fix will be ready or if we find any workaround that may help in this case.