`<summary for>` pointing to a `<details>` element elsewhere
Open
Nobody has claimed this yet.
details
needs-triage
- Dominant language
- MDX
- Stars
- 4.5k
- Forks
- 226
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 4
Description
Since we're on to making simple improvements to <details>, how about this: a for attribute on <summary> which can point to a <details> element by id, allowing them to be in entirely separate parts of the DOM. This would address the common author need to have toggles in separate places from the toggled content, is pretty straightforward in terms of syntax, and follows established markup patterns.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no repository files, tests, or entry points, so begin by locating where Open UI defines or discusses
and . Establish the behavior and acceptance criteria for a
. Establish the behavior and acceptance criteria for a reference to a separate element; done requires an agreed specification change and any corresponding repository updates.
element; done requires an agreed specification change and any corresponding repository updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100