Skip to content

fix(watch-only): keep balance refresh button available in watch-only mode#279

Merged
BitHighlander merged 1 commit into
developfrom
fix/watchonly-refresh-button
Jun 21, 2026
Merged

fix(watch-only): keep balance refresh button available in watch-only mode#279
BitHighlander merged 1 commit into
developfrom
fix/watchonly-refresh-button

Conversation

@BitHighlander

Copy link
Copy Markdown
Collaborator

Summary

The Dashboard top-right utility row (Reports + Audit + Refresh) was wrapped entirely in {!watchOnly && (...)}, so watch-only mode hid the Refresh balances button along with the management actions.

Refreshing balances is a safe, read-only action — there's no reason to hide it from watch-only users. (The per-asset refresh button in AssetPage.tsx was already always-visible, so the two refresh controls behaved inconsistently.)

Change

  • Keep the utility row and its Refresh button rendered in both modes.
  • Gate only Reports and Audit (management/signing-adjacent actions) on !watchOnly.
  • Watch-only banner and all signing actions (Send/Swap/Privacy) remain hidden as before.

Test plan

  • Full mode: Reports, Audit, Refresh all visible (unchanged).
  • Watch-only mode: Refresh visible and functional; Reports/Audit hidden; watch-only banner still shows.

…mode

The Dashboard top-right utility row was fully hidden in watch-only mode,
which also hid the read-only Refresh balances button. Refreshing balances
is a safe read-only action and should remain available to watch-only
users. Gate only Reports and Audit (management actions) on !watchOnly;
keep the row and its Refresh button rendered in both modes.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@BitHighlander
BitHighlander merged commit 9655ed3 into develop Jun 21, 2026
1 check passed
@BitHighlander
BitHighlander deleted the fix/watchonly-refresh-button branch June 21, 2026 00:32
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