fix: use formatAddressHtml in receive view for display consistency #69
Reference in New Issue
Block a user
Delete Branch "fix/issue-58-receive-address-consistency"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The receive view was using raw
textContentand a manually constructed color dot instead of the sharedformatAddressHtmlhelper used by other views. This violated the display consistency policy ("Same data formatted identically across all screens").Changes
formatAddressHtml()to render address with color dot, title (e.g. "Wallet 1 — Address 1"), and ENS name — matchingaddressDetailreceive-dot/receive-addressspans with a singlereceive-address-blockelementdocker build .passes.Closes #58
The receive view was using raw textContent and a manually constructed color dot instead of the shared formatAddressHtml helper used by other views. This violated the display consistency policy ('Same data formatted identically across all screens'). Changes: - Use formatAddressHtml() to render address with color dot, title (e.g. 'Wallet 1 — Address 1'), and ENS name — matching addressDetail - Make the address block itself click-to-copy (matching policy: 'Clicking any address copies the full untruncated value') - Replace separate receive-dot/receive-address spans with a single receive-address-block element - Address is still shown in full (no truncation) as appropriate for the receive view Closes #58Review: ✅ Approved
Build:
docker build .passes.Changes reviewed:
formatAddressHtml()+addressTitle()helpersdataset.full, matching the display consistency policydataset.fullsourcereceive-address-blockThis properly fixes #58. Ready to merge.