Repository navigation
[Bug] <details> content is not padded beneath its <summary>. #1811
Description
Activity
- changed the title
[-]`<details>` tag content is not padded correctly.[/-][+]`<details>` content is not padded beneath its `<summary>`.[/+]on Jun 12, 2024 Stale issue message
Reacted by Mr Beedell, Roke Julian LockhartReacted by Mr Beedell, Roke Julian LockhartStale issue message
Reacted by Mr Beedell, Roke Julian LockhartReacted by Mr Beedell, Roke Julian LockhartThis issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Reacted by Mr Beedell, Roke Julian LockhartThis issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Reacted by Mr Beedell, Roke Julian Lockhart1 remaining item
- changed the title
[-]`<details>` content is not padded beneath its `<summary>`.[/-][+][Bug] `<details>` content is not padded beneath its `<summary>`.[/+]on Jun 16, 2025 This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Reacted by Mr Beedell, Roke Julian LockhartI've since ascertained that
<p></p><details><p></p>and<p></p></details><p></p>remediate this.This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Reacted by Mr Beedell, Roke Julian LockhartThanks for reporting this.
After investigating, this issue is about padding on
<details>elements, which is handled by GitHub.com's frontend CSS — not by this repository.This repo (
github/markup) only handles step 1 of the rendering pipeline: converting markup formats (RST, AsciiDoc, MediaWiki, etc.) to raw HTML. Check out this part of the README for a fuller picture:Please note that only the first step is covered by this gem — the rest happens on GitHub.com's backend.
CSS styling, padding, margins, and image sizing are all applied downstream by GitHub.com's frontend. This repo has no control over those.
For CSS/styling feedback, GitHub's feedback discussions would be the right place to raise this.
Closing as out of scope for this repository.
I have re-submitted this at
orgs/community/discussions/193801. @zkoppert, please re-close as invalid.
Errata (Examples)
…renders as:
Browser
Screenshot
Evidently, the padding is inconsistent.
Affected
As bypassed, as
#issuecomment-3193630451explains:Details
ActivityWatch/aw-qt/issues/113issues/2005#issue-3553990404mysociety/alaveteli/issues/8958#issue-3566436614dotnet/runtime/issues/122721#issuecomment-3690557017element-hq/element-web/issues/29244#issue-2845987401webcompat/web-bugs/issues/199619#issue-3798405115postgres-ai/postgres_ai/issues/24#issue-3806430202canonical/ubuntu.com/issues/14859#issuecomment-3784475313ksnip/ksnip/issues/1119#issue-3060851532issues/2000#issue-3522107604orgs/community/discussions/162311#discussioncomment-15667344opencollective/opencollective/issues/8593#issue-3980347589quickemu-project/quickemu/issues/1902#issue-4244237317quickemu-project/quickemu/issues/1903#issue-4244319455warpdotdev/warp/issues/9211#issuecomment-4361821404