Skip to content

Fix iOS touch issue on v-close-popper #1077

New issue

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

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

Already on GitHub? # to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

navyCarpet
Copy link

This PR fixes an issue where the v-close-popper directive, when used on a router-link, would only close the popper without navigating page on iOS.

caused by touchstart passive option
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @navyCarpet, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request addresses an issue where the v-close-popper directive, when applied to a router-link on iOS devices, would only close the popper without navigating to the new page. The fix involves conditionally disabling the touchstart event listener based on whether the device is running iOS.

Highlights

  • Bug Fix: Addresses an issue where v-close-popper prevented navigation on iOS devices when used with router-link.
  • Conditional Event Listener: The touchstart event listener is now conditionally added based on whether the device is running iOS.

Changelog

  • packages/floating-vue/src/directives/v-close-popper.ts
    • Imported isIOS from ../util/env.
    • Conditionally disabled the touchstart event listener on iOS devices by adding !isIOS to the condition supportsPassive && !isIOS on line 6.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


On iOS, a tap's delay,
A popper closed, the page astray.
With nimble fix,
Navigation mix,
Now routes work without dismay.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This PR addresses an issue where the v-close-popper directive, when used on a router-link, would only close the popper without navigating page on iOS. The solution involves conditionally applying the passive listener option based on whether the device is an iOS device. This seems like a reasonable approach to address the reported issue.

Merge Readiness

The code change appears straightforward and addresses the described issue. Given the targeted fix for iOS and the use of feature detection (isIOS), the risk of unintended side effects seems low. I am unable to directly approve the pull request, and users should have others review and approve this code before merging. The change seems reasonable and I would recommend merging it after another review.

Copy link

netlify bot commented Apr 24, 2025

Deploy Preview for v-tooltip ready!

Name Link
🔨 Latest commit 82fc6a4
🔍 Latest deploy log https://app.netlify.com/sites/v-tooltip/deploys/680a7b38c999fc0008f52b83
😎 Deploy Preview https://deploy-preview-1077--v-tooltip.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@navyCarpet
Copy link
Author

Another way could be to add modifiers that disable the passive. I look forward to comment.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant