Repository navigation
fix: stop the detail page title rendering a literal · - #3
Merged
Merged
Conversation
page() escapes what it is handed, so the entity in the detail page title became &middot;. Long-standing in <title>, but the OpenGraph metadata now feeds the same string to og:title, so a status link pasted into Discord unfurled with · in the headline. The other two · uses sit in body HTML that is not escaped, so they stay. Co-Authored-By: Claude Opus 5 <noreply@anthropic.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
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.
detailPagebuilt its title as${alert.title} · ${SITE_NAME}, andpage()escapes whatever it is handed — so the entity became&middot;and rendered as the literal text·.Long-standing in
<title>, but newly visible: the OpenGraph metadata added in #1 feeds the same string toog:title, so a status link pasted into Discord unfurled with·in the headline. Which is where these links get shared.Fixed by using a literal
·— the output is UTF-8, so it needs no entity. The two other·uses are untouched: they sit in body HTML that is not passed throughescape().Before:
After:
🤖 Generated with Claude Code