header: draw the nav caret as a chevron, large enough to read - #45
Merged
Conversation
The SVG that replaced the substituted U+25BE glyph was a filled wedge 7px wide and 4.5px tall. At 14px that collapses into a mark that reads as a full stop - which is what the fallback glyph looked like, so the symptom survived the fix that removed its cause. A two-stroke chevron with round caps at 14px stays legible at this size, and sits better with the hairline borders and underline rules used elsewhere. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Picks up the chevron caret. Built from a cleared .next, per the stale-utility problem found in the previous snapshot commit. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Turbopack's incremental build does not always evict a Tailwind utility whose last use has just been deleted. The CSS chunk is named after its own content hash, so the snapshot then disagrees with a clean build - which is how two snapshot commits reached CI carrying rules for classes that were no longer in any component. sync:static now clears .next and out before building, so the snapshot is reproducible by construction rather than by remembering. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Picks up the chevron caret, built from a cleared cache. Verified byte-identical to what the CI runner produces. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
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
1 participant
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.
What
Follow-up to #44. The caret was reported as still looking wrong, and it was.
Replacing the substituted
▾glyph with an SVG removed the cause — a character outside the Space Mono subset, rendered by whatever font the OS supplies — but the replacement I drew was a filled wedge 7px wide and 4.5px tall. At 14px that collapses into a mark that reads as a full stop, which is exactly what the substituted glyph looked like. So the symptom outlived the fix.It is now a two-stroke chevron with round caps at 14px, which stays legible at this size and sits better with the hairline borders and underline rules used elsewhere on the site.
Verified
rotate: 180deg, and the dropdown still lists all five sub-tabs..next, per the stale-utility problem found in team: drop Human Generated, and draw the nav caret instead of typing it #44 — confirmed the removedtext-[0.65em]utility is absent from the shipped CSS.Note on the rest of the header
The other three nav items are provably consistent with
Portfolio: same family,font-weight: 400,14px,letter-spacing: normal, measured on the live site.Portfolioonly differs in colour, becauseisActivekeeps it active across its sub-tabs — full-opacity text on a dark ground simply reads heavier than the muted 52% used for the inactive items. That is the intended active state, not a font difference.