Put Mail and Blogs in the portal tab strip #226

2026-09-25T14:10:28Z

paulhitt commented

2026-09-25 14:10:28 +00:00

(Migrated from gitlab.com)

The tab strip at the top of every page had drifted from the one on flamenet.io, which carries Mail directly after Messenger and Blogs at the end. This one carried neither, so two of the portal's sections were unreachable from anywhere on this domain.

Home  News  Directory  Games  Messenger (separate app)  Mail  Events  Forums  Radio  Answers  Groups  Blogs

Checked the live portal first rather than assuming: flamenet.io already renders both tabs, and its theme fallback has had them all along. The gap was only here.

Why nothing caught it

The strip is static markup in layout.leaf, and every suite that renders a page inspects the page rather than the chrome around it. A dropped tab would have shipped silently on every page of the site.

The new test reads the strip out of two rendered pages and asserts order, not just presence: Mail between Messenger and Events, Blogs after Groups with no <li> following it. A check for the string alone would pass with Mail sitting at the far end of the strip.

Falsified twice, by moving Mail to the end and by appending a tab after Blogs. Each fails on the assertion it should, naming the page.

One change that was not asked for

Messenger(separate app) was missing its space. flamenet.io renders the same tab with the space, so this was a typo on every page of this site. Called out here rather than slipped in; it is one line to revert.

753 tests in 78 suites, no failures.

🤖 Generated with Claude Code

The tab strip at the top of every page had drifted from the one on flamenet.io, which carries **Mail** directly after Messenger and **Blogs** at the end. This one carried neither, so two of the portal's sections were unreachable from anywhere on this domain. ``` Home News Directory Games Messenger (separate app) Mail Events Forums Radio Answers Groups Blogs ``` Checked the live portal first rather than assuming: flamenet.io already renders both tabs, and its theme fallback has had them all along. The gap was only here. ### Why nothing caught it The strip is static markup in `layout.leaf`, and every suite that renders a page inspects the page rather than the chrome around it. A dropped tab would have shipped silently on every page of the site. The new test reads the strip out of two rendered pages and asserts **order**, not just presence: Mail between Messenger and Events, Blogs after Groups with no `<li>` following it. A check for the string alone would pass with Mail sitting at the far end of the strip. Falsified twice, by moving Mail to the end and by appending a tab after Blogs. Each fails on the assertion it should, naming the page. ### One change that was not asked for `Messenger(separate app)` was missing its space. flamenet.io renders the same tab with the space, so this was a typo on every page of this site. Called out here rather than slipped in; it is one line to revert. --- **753 tests in 78 suites, no failures.** 🤖 Generated with [Claude Code](https://claude.com/claude-code)

paulhitt commented

2026-09-25 14:45:11 +00:00

(Migrated from gitlab.com)

mentioned in commit f5087e8a48

mentioned in commit f5087e8a48524167de363bfa484649bd7829de74

paulhitt (Migrated from gitlab.com) merged commit f5087e8a48 into main

2026-09-25 14:45:11 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: extant2000/flamenet-relay#226