feat(frontend): support details/summary in article content - #259
Merged
Conversation
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.
Closes #258
Changes
detailsandsummaryto the DOMPurify tag allowlist infrontend/src/lib/content.ts, plus theopenattribute so feeds that ship<details open>keep their expanded state.<summary>from the empty-wrapper removal pass — a<details>without a summary has no disclosure toggle and its content becomes unreachable.details/summarymatching the existing flow rhythm.Steam News-style feeds with collapsible changelogs/patch notes now render as native expandable sections.
Verified with
npx tsc -b --noEmit(no test suite exists for the frontend).