Skip to content

Help page /help/faq/editing renders orphaned markdown reference-link definitions as visible junk (literal <br />, escaped chars) #13074

Description

@lokesh

Problem

The bottom of https://openlibrary.org/help/faq/editing (just below the "What is a web book?" section, immediately above the History panel) renders a block of broken text. It is a leftover set of markdown footnote / reference-link definitions — [23]: through [32]: — that are printed as visible raw text and links instead of being collapsed into invisible reference definitions. Inline markup inside the block also leaks through as literal text.

What renders incorrectly

All of these are localized to that one trailing block (the rest of the page is fine):

Issue Count Example (as shown to users)
Literal <br /> shown as text 9 …Red_Pony_Tortilla<br /> [24]: — the renderer HTML-escapes it to &lt;br /&gt;
Visible [n]: reference markers 10 [23]:, [24]:[32]:
Backslash-escaped chars shown literally Tales_from_Shakespeare\_(20)
URL-encoded backslash leaking through 1 %5C_(20)
Links whose visible text is a raw URL 10 the openlibrary.org/works/… citation links

Steps to reproduce

  1. Visit https://openlibrary.org/help/faq/editing
  2. Scroll to the bottom of the article, after the "What is a web book?" section and just above the History panel.
  3. Observe the block of [23]: <url> <br /> [24]: <url> … rendered as visible junk.

Likely cause

This help page is an Infogami wiki page (history shows it as "Copy from /help/faq/editing"). Its source contains an orphaned block of markdown reference-link / footnote definitions — citation cruft, likely from a copy/import. Open Library's markdown renderer is not treating these as invisible link reference definitions, so they print as visible text, and embedded <br /> separators are HTML-escaped and shown literally.

Suggested fix

  1. Remove the orphaned reference-definition / footnote block from the page source.
  2. Investigate why these markdown reference definitions render visibly as text rather than being parsed as link reference definitions.

Environment: openlibrary.org production · observed 2026-06-30

Metadata

Metadata

Assignees

Labels

Lead: @lokeshIssues pertaining to front-end design system [css, js, components]Type: BugSomething isn't working. [managed]

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions