Skip to content

Conversation

@smgv
Copy link
Contributor

@smgv smgv commented Jan 27, 2026

Motivation and Context

Jira Link:

Description

In this PR, I have updated the ConnectWalletQRCode handling for wallet links. The component is no longer rendered when the walletRegistry app list is empty. Additionally, we now validate platform-specific keys—browser for desktop and ios/android for mobile—to ensure the correct platforms are available.

We also disabled the back button when the bottom sheet is opened.

How has this been tested?

Screenshots (if appropriate):

Screenshot 2026-01-27 at 5 53 33 PM
Screen.Recording.2026-01-27.at.5.53.42.PM.mov

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

  • My code follows the code style of this project. (run lint)
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • My code requires a db migration.

Note

Refines wallet connection UX and bottom sheet behavior.

  • ConnectWalletQrCode now shows the "Get wallet" CTA only when wallet registry has platform-appropriate links (desktop: browser/chrome/firefox/edge, mobile: ios/android); requires and uses platform prop passed from Root and ConnectWallet
  • ConnectWalletHeader API updated: adds hideBackButton; back button respects disableBackButton (disabled state and click ignored); ConnectWallet computes hideBackButton and forwards disableBackButton from Root (disabled when installLinks or multiChainSelector sheets are open)
  • BottomSheet backdrop click now stops event propagation before closing to avoid accidental parent handlers

Written by Cursor Bugbot for commit 470d069. This will update automatically on new commits. Configure here.

@smgv smgv requested a review from chaitanyapotti January 27, 2026 12:33
@smgv smgv self-assigned this Jan 27, 2026
@vercel
Copy link

vercel bot commented Jan 27, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
web3auth-web Ready Ready Preview, Comment Jan 27, 2026 3:32pm

Request Review

Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

selectedButton={bodyState.metamaskQrCode.wallet}
primaryColor={bodyState.metamaskQrCode.wallet.walletRegistryItem?.primaryColor}
logoImage={`https://images.web3auth.io/login-${bodyState.metamaskQrCode.wallet.name}.${bodyState.metamaskQrCode.wallet.imgExtension}`}
platform={deviceDetails.platform}
Copy link

Choose a reason for hiding this comment

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

Missing disableBackButton prop in MetaMask QR code view

Medium Severity

The ConnectWalletHeader in the MetaMask QR code view is missing the disableBackButton prop. The PR adds disableBackButton={bodyState.installLinks?.show || bodyState.multiChainSelector?.show} to the main ConnectWallet component, but the ConnectWalletHeader rendered when bodyState.metamaskQrCode?.show is true doesn't receive this prop. When a user opens the "Get Wallet" install links bottom sheet from the MetaMask QR code view, the back button remains enabled instead of being disabled, which is inconsistent with the stated PR behavior.

Additional Locations (1)

Fix in Cursor Fix in Web

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.

2 participants