Replace Mermaid flow charts with a readable, dependency-free CSS step-flow#6
Open
mxinden-bot wants to merge 2 commits into
Open
Replace Mermaid flow charts with a readable, dependency-free CSS step-flow#6mxinden-bot wants to merge 2 commits into
mxinden-bot wants to merge 2 commits into
Conversation
Mermaid centered message labels over the middle DNS lifeline, so they read behind the lines, and its injected styles resisted a CSS halo fix. Replace the two diagrams with a small CSS step-flow (one row per hop: a '-> DNS' / '<-> server' badge plus the action, grouped by connection). No lifelines means nothing to overlap; it matches the site's look and drops the ~1MB Mermaid CDN dependency and its lazy-loader.
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ❌ Deployment failed View logs |
savearoundtrip | b570540 | Jun 09 2026, 11:02 AM |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Valentin noted that text in the flow charts sits behind the lines. Root cause: Mermaid centers each message label over its arrow, and the Client↔Server arrows cross the middle DNS lifeline, so labels land on top of that vertical line. A CSS "halo" didn't stick (Mermaid's own injected styles override it), and dropping DNS to a note (already reverted) lost the actor and looked worse. Even reordering participants only half-fixes it (the long
alpn=h3 + IP hints (+ECH)label would still cross a lifeline).What
Drop Mermaid for the two diagrams and render them as a small, dependency-free CSS step-flow: one row per hop, a
→ DNS/↔ serverbadge plus the action, grouped by "first connection" / "second connection". No lifelines, so nothing can overlap.Keeps all the substance:
Bonus
Removes the ~1 MB Mermaid CDN module and its IntersectionObserver lazy-loader. The diagrams now render instantly with no JS and no third-party fetch, and they inherit the site's own fonts/colors.
Notes
🤖 Generated with Claude Code
Generated by Claude Code