Skip to content

fix(masking): default MetaMask masking ON; readable contrast on Settings text#63

Merged
BitHighlander merged 1 commit intodevelopfrom
fix/masking-default-and-contrast
May 1, 2026
Merged

fix(masking): default MetaMask masking ON; readable contrast on Settings text#63
BitHighlander merged 1 commit intodevelopfrom
fix/masking-default-and-contrast

Conversation

@BitHighlander
Copy link
Copy Markdown
Collaborator

Two issues on the Side Panel → Settings → "Enable Masking" surface

1. MetaMask masking now defaults to ON

CowSwap and several swap aggregators bail out of their connect flow without a window.ethereum carrying isMetaMask: true. Modern dApps that discover wallets via EIP-6963 still see KeepKey as itself, so flipping the default is purely additive — sites that work with the masking off still work, and sites that need it stop being broken on first install.

Existing installs keep whatever they previously set (chrome.storage persists the boolean once it's been read). Only fresh installs / cleared storage pick up the new default. If we want to forcibly upgrade existing users (e.g. one-time migration that flips false→true once), that's a separate change — call it out and I'll add it.

2. The body-text labels were unreadable

color="gray.500" is fine on a light background but the side panel's dark theme makes it ~black-on-black. The two affected lines are the MetaMask description and the conflict-warning under the Coming Soon rows — the latter being exactly the part the user most needs to see.

Switched both to color="whiteAlpha.700", the codebase convention for secondary copy on dark surfaces (used in Connect.tsx, Balances.tsx, Tokens.tsx, CustomTokenDialog.tsx).

Files

  • packages/storage/lib/customStorage.tsenableMetaMaskMasking: falsetrue in the masking-settings storage default.
  • pages/side-panel/src/components/Settings.tsx — two gray.500whiteAlpha.700 color swaps.

Test plan

  • Fresh install (or: clear extension storage) → Settings shows MetaMask Masking toggle ON.
  • Visit cowswap.exchange / 1inch / similar — connect flow lights up KeepKey.
  • Both description blurbs are readable on the dark Settings background.
  • Toggling off → on → off persists across reload.

🤖 Generated with Claude Code

…ngs text

Two pain points reported on the side-panel Settings screen.

1) MetaMask masking now defaults to ON. CowSwap and several aggregators expect a window.ethereum with isMetaMask:true and bail out of their connect flow without it. Modern dApps that discover wallets via EIP-6963 still see KeepKey as itself, so this is purely additive coverage. Existing installs keep whatever they previously set; only fresh installs (or storage resets) pick up the new default.

2) The two body-text labels under "Enable Masking" used color="gray.500" which is unreadable on the side panel's dark background — black-on-black for the part the user most needs to see (the conflict warning). Switched to whiteAlpha.700, the codebase convention for secondary copy on dark surfaces (Connect.tsx, Balances.tsx, Tokens.tsx, CustomTokenDialog.tsx all use it).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@BitHighlander BitHighlander merged commit f2b47f7 into develop May 1, 2026
4 of 5 checks passed
@BitHighlander BitHighlander deleted the fix/masking-default-and-contrast branch May 1, 2026 02:48
BitHighlander added a commit that referenced this pull request May 1, 2026
Cumulative since 0.0.28:

  #57 feat: Pioneer-sourced EVM chain registry + Solana sign-message UX
  #58 feat(ux): risk-tiered approval colors, hex dump + copy, deep-link Chainlist, typed timeouts
  #59 fix(eth): RPC failover on broadcast + pin networks on JsonRpcProvider
  #60 fix(audit): UTXO build race + cross-chain broadcast resilience + read failover
  #61 fix: drop orphaned approval events on service-worker startup
  #62 fix(eth): read handlers participate in failover; method-rejection counted as transient
  #63 fix(masking): default MetaMask masking ON; readable contrast on Settings text

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.

1 participant