Bug Description
The handleCopyHash function in TransactionCard.tsx calls navigator.clipboard.writeText() without awaiting the returned Promise. This causes a false success toast to appear even when the clipboard write fails, and silently swallows any errors.
Expected Behavior
toast.success("Transaction hash copied!") should only fire after a confirmed successful write.
- On failure, a
toast.error(...) should be displayed.
Steps to Reproduce
- Open a transaction in the UI
- Click the Copy Hash button
- Simulate a clipboard failure (e.g. revoke clipboard permission in browser settings, or serve over HTTP)
- Observe that the success toast still appears despite the failure
Logs and Screenshots
N/A — Bug is reproducible via code inspection.
Environment Details
- OS: Windows 11
- Browser: Chrome
Impact
Low - Minor inconvenience
Code of Conduct
Bug Description
The
handleCopyHashfunction inTransactionCard.tsxcallsnavigator.clipboard.writeText()without awaiting the returned Promise. This causes a false success toast to appear even when the clipboard write fails, and silently swallows any errors.Expected Behavior
toast.success("Transaction hash copied!")should only fire after a confirmed successful write.toast.error(...)should be displayed.Steps to Reproduce
Logs and Screenshots
N/A — Bug is reproducible via code inspection.
Environment Details
Impact
Low - Minor inconvenience
Code of Conduct