Repository navigation
Docs: move <details> usage notes out of Try It, fix ::details-content animation claim - #45218
BHUVANSH855 wants to merge 5 commits into
Conversation
… animation claim (mdn#42226)
github-actions
Bot
added
Content:HTML
|
Preview URLs (1 page) (comment last updated: 2026-08-23 12:29:09) |
Co-authored-by: wbamberg <will@bootbonnet.ca>
Co-authored-by: wbamberg <will@bootbonnet.ca>
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
|
The change at 8f921a1 doesn't address my comment. |
|
Closing this because it still hasn't addressed my feedback. |
|
Which comment was this blocked on? |
|
#45218 (comment) - I made a suggestion with a cssxref macro call that I wasn't sure about, and asked the author to check the syntax and make sure it worked. |
|
I see. The macro call was replaced with FYI you just need to write |
|
Can it be reopened now. |
|
Once your other PRs are merged, it will be possible to reopen this one. There's a limit of three simultaneously opened PRs. |
we can reopen this as draft or i will convert other to draft whatever suits. Let me know whatever i have to do. |
5 participants
Description
Moves the descriptive prose about the
<details>disclosure widget out of the "Try it" interactive-example block and into a new "Usage notes" section, and corrects the outdated claim that there's no built-in way to animate the open/closed transition.Motivation
The "Try it" section should only contain the interactive demo, not explanatory prose — the surrounding text was left over from before MDN content moved to GitHub and predates that convention. Separately, the text stated there's "no built-in way to animate the transition between open and closed," which is no longer true:
::details-contentsupports this and has been Baseline since September 2025. This PR relocates the prose into a new "Usage notes" section (placed after "Events" and before "Examples") and updates the animation claim to point readers to::details-content.Additional details
::details-contenton MDNRelated issues and pull requests
Fixes #42226
From #42226 (comment)