The invoice detail and a domain's DNS records still render a back link #321

New Issue

2026-11-02T07:19:09Z

cgalo5758 commented

2026-11-02 07:19:09 +00:00

What happens

Two member views open in place of their region and offer "← Back to …" to return, which the chrome conventions forbid ("Pages SHALL NOT render '← Back to {parent}' links or any other back affordance"; the location trail above the title is the way back):

the invoice detail, swapped into the Billing page's #billing-content, with "← Back to invoices" (member_invoice_detail.html);
a domain claim's DNS records, swapped into the nearest .domains-surface, with "← Back to domains" (member_domains_claim.html).

The page header above each stays the page's ("Billing", "Dashboard"), so the title names a page the content no longer is. On the dashboard the domain claim's back link also lands in the wrong place: the claim opens from the "Domain verification in progress." notice at the top of the dashboard, and "Back to domains" swaps the domains table (/partials/domains/claims: every claim with its Details, Release and DNS records controls) into that spot, a second copy of the table the FedWiki sites card already shows, where the notice was.

No check refuses a back link. The anatomy lint (internal/lint/anatomy.go) has rules for titles, badges, empty states, forms and notices but none for a back affordance, and make screens captures pages at rest, never a region a click swaps in.

What should happen

Neither view renders a back affordance. Each either becomes a page with its own location trail (for example "Home / Billing / Invoice …") or opens without replacing its surroundings, the way the FedWiki create form opens in the shared dialog; leaving it returns the region to what it showed before. The anatomy lint refuses a "Back to" link or ← in any template, fragments included, so a third cannot appear.

Where

internal/embeds/templates/partials/member_invoice_detail.html (line 14), internal/embeds/templates/partials/member_domains_claim.html (line 15), the dashboard's .domains-surface in internal/embeds/templates/index.html, and lineRules in internal/lint/anatomy.go.

Steps

As a member with a pending domain claim, open the dashboard and press "View DNS records" in "Domain verification in progress.". The DNS records replace the notice under the "Dashboard" title, with "← Back to domains" above them.
Press "← Back to domains". The domains table appears at the top of the dashboard instead of the notice; the sites card further down shows the same table.
On Billing, open an invoice. "← Back to invoices" appears under the "Billing" title.

Why it matters

The trail is the one statement of where a view sits, and below the lg breakpoint the rail is a drawer, so a view that swaps out its page's content while keeping the page's title leaves a member on a screen whose title is wrong and whose way back is a one-off control. On the dashboard that control also leaves a duplicate table behind.

### What happens Two member views open in place of their region and offer "← Back to …" to return, which the chrome conventions forbid ("Pages SHALL NOT render '← Back to {parent}' links or any other back affordance"; the location trail above the title is the way back): - the invoice detail, swapped into the Billing page's `#billing-content`, with "← Back to invoices" (`member_invoice_detail.html`); - a domain claim's DNS records, swapped into the nearest `.domains-surface`, with "← Back to domains" (`member_domains_claim.html`). The page header above each stays the page's ("Billing", "Dashboard"), so the title names a page the content no longer is. On the dashboard the domain claim's back link also lands in the wrong place: the claim opens from the "Domain verification in progress." notice at the top of the dashboard, and "Back to domains" swaps the domains table (`/partials/domains/claims`: every claim with its Details, Release and DNS records controls) into that spot, a second copy of the table the FedWiki sites card already shows, where the notice was. No check refuses a back link. The anatomy lint (`internal/lint/anatomy.go`) has rules for titles, badges, empty states, forms and notices but none for a back affordance, and `make screens` captures pages at rest, never a region a click swaps in. ### What should happen Neither view renders a back affordance. Each either becomes a page with its own location trail (for example "Home / Billing / Invoice …") or opens without replacing its surroundings, the way the FedWiki create form opens in the shared dialog; leaving it returns the region to what it showed before. The anatomy lint refuses a "Back to" link or `←` in any template, fragments included, so a third cannot appear. ### Where `internal/embeds/templates/partials/member_invoice_detail.html` (line 14), `internal/embeds/templates/partials/member_domains_claim.html` (line 15), the dashboard's `.domains-surface` in `internal/embeds/templates/index.html`, and `lineRules` in `internal/lint/anatomy.go`. ### Steps 1. As a member with a pending domain claim, open the dashboard and press "View DNS records" in "Domain verification in progress.". The DNS records replace the notice under the "Dashboard" title, with "← Back to domains" above them. 2. Press "← Back to domains". The domains table appears at the top of the dashboard instead of the notice; the sites card further down shows the same table. 3. On Billing, open an invoice. "← Back to invoices" appears under the "Billing" title. ### Why it matters The trail is the one statement of where a view sits, and below the lg breakpoint the rail is a drawer, so a view that swaps out its page's content while keeping the page's title leaves a member on a screen whose title is wrong and whose way back is a one-off control. On the dashboard that control also leaves a duplicate table behind.

cgalo5758 added the

kind

bug

area/member-ui area/testing labels 2026-11-02 07:19:09 +00:00

cgalo5758 referenced this issue

2026-11-02 07:44:12 +00:00

A notice lists its own rows, each with its words and one link #323

cgalo5758 added this to the Public launch milestone 2026-11-02 08:45:55 +00:00

Sign in to join this conversation.