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

fix: interactive elements tot responding on mobile #4320

Closed
wants to merge 2 commits into from
Closed

Conversation

sudongyuer
Copy link
Member

@sudongyuer sudongyuer commented Dec 10, 2024

Closes: #4292

📝 Description

Using onClick to handler the event :

⛳️ Current behavior (updates)

1_1733848569.mp4

🚀 New behavior

3_1733848572.mp4

💣 Is this a breaking change (Yes/No):

📝 Additional Information

This PR also will solve Card component event not work on mobile

Summary by CodeRabbit

  • Bug Fixes

    • Resolved issues with interactive elements not responding on mobile devices, improving usability.
  • New Features

    • Introduced a new property, allowTextSelectionOnPress, allowing text selection on pressable elements for enhanced functionality.

Copy link

changeset-bot bot commented Dec 10, 2024

🦋 Changeset detected

Latest commit: 7d5f36f

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 16 packages
Name Type
@nextui-org/use-aria-button Patch
@nextui-org/autocomplete Patch
@nextui-org/button Patch
@nextui-org/calendar Patch
@nextui-org/card Patch
@nextui-org/modal Patch
@nextui-org/popover Patch
@nextui-org/select Patch
@nextui-org/use-aria-toggle-button Patch
@nextui-org/react Patch
@nextui-org/alert Patch
@nextui-org/date-picker Patch
@nextui-org/drawer Patch
@nextui-org/dropdown Patch
@nextui-org/navbar Patch
@nextui-org/snippet Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link
Contributor

coderabbitai bot commented Dec 10, 2024

Walkthrough

This pull request introduces a patch for the @nextui-org/use-aria-button package, addressing an issue where interactive elements were unresponsive on mobile devices. The changes include the addition of a new property, allowTextSelectionOnPress, to the AriaButtonProps type in the useAriaButton function. This enhancement allows text selection on pressable elements while maintaining the existing functionality and structure of the component.

Changes

File Path Change Summary
.changeset/wicked-melons-promise.md Patch added for @nextui-org/use-aria-button addressing mobile interactivity issues.
packages/hooks/use-aria-button/src/index.ts Updated AriaButtonProps to include allowTextSelectionOnPress; modified logic in useAriaButton to utilize this property.

Assessment against linked issues

Objective Addressed Explanation
Interactive elements should respond to taps or clicks on iOS devices (Issue #4292)

Possibly related PRs

Suggested reviewers

  • jrgarciadev
  • wingkwong

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Experiment)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

vercel bot commented Dec 10, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
nextui-docs-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 10, 2024 4:39pm
nextui-storybook-v2 ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 10, 2024 4:39pm

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between a289ff8 and 7d5f36f.

📒 Files selected for processing (2)
  • .changeset/wicked-melons-promise.md (1 hunks)
  • packages/hooks/use-aria-button/src/index.ts (0 hunks)
💤 Files with no reviewable changes (1)
  • packages/hooks/use-aria-button/src/index.ts
🧰 Additional context used
🪛 LanguageTool
.changeset/wicked-melons-promise.md

[uncategorized] ~5-~5: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...patch --- fix interactive elements tot responding on mobile

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)

🔇 Additional comments (1)
.changeset/wicked-melons-promise.md (1)

1-3: LGTM on the patch version bump

The patch version bump is appropriate for this bug fix addressing mobile interactivity issues, as it doesn't introduce breaking changes.

"@nextui-org/use-aria-button": patch
---

fix interactive elements tot responding on mobile
Copy link
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue

Fix typo in the changeset description

There's a typo in the description that affects clarity.

Apply this fix:

-fix interactive elements tot responding on mobile
+fix interactive elements not responding on mobile
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
fix interactive elements tot responding on mobile
fix interactive elements not responding on mobile
🧰 Tools
🪛 LanguageTool

[uncategorized] ~5-~5: This verb may not be in the correct form. Consider using a different form for this context.
Context: ...patch --- fix interactive elements tot responding on mobile

(AI_EN_LECTOR_REPLACEMENT_VERB_FORM)

@jrgarciadev
Copy link
Member

Complete fix here: #4322

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

Successfully merging this pull request may close these issues.

[BUG] - Interactive Elements Not Responding on iOS After Updating to NextUI 2.6.0
2 participants