Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sidenav - On a iPhone, need to tap the link twice to make the page transition. #1659

Closed
makots opened this issue May 17, 2023 · 0 comments · Fixed by #1824
Closed

Sidenav - On a iPhone, need to tap the link twice to make the page transition. #1659

makots opened this issue May 17, 2023 · 0 comments · Fixed by #1824
Assignees
Milestone

Comments

@makots
Copy link

makots commented May 17, 2023

Describe the bug
When sidenav is displayed, tapping a link only displays a scroll bar and does not take you to the link.
If the link is tapped again, it will take you to the link.

Reproduces on iPhone, but not on android or desktop.

To Reproduce
Steps to reproduce the behavior:

  1. On a iPhone, go to https://tailwind-elements.com/
  2. Tap the menu icon in the upper left corner
  3. Tap "Tailwind Elements" at the top of Sidenav
  4. Links do not work, only scroll bars appear
  5. Tap "Tailwind Elements" again
  6. Links do work correctly

Expected behavior
Whenever you tap a link, you will be redirected to the link.

Actual behavior
When the scrollbar is not displayed on sidenav, tapping a link does not take you to the link.

Smartphone:

  • Device: iPhone 12 Pro
  • OS: iOS 16.4.1 (a)
  • Browser Safari 604.1 / Chrome 113.0.5672.69

Additional context
If you change sidenav to not use perfect-scrollbar, this problem will not reproduce.

@juujisai juujisai added this to the v1.0.0-beta3 milestone May 17, 2023
@juujisai juujisai self-assigned this Jul 6, 2023
@juujisai juujisai linked a pull request Jul 25, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants