Use case: Replace IDREF DOM content attribute associations with a JavaScript element reference
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 603
- Forks
- 61
- PR merge metrics
- No merged PRs in 30d
Description
Use case: Replace IDREF content attr associations with a JavaScript element reference
Some HTML and ARIA features require reference to another element by IDREF, but it's problematic in some contexts to require the accessibility code to generate IDs. For example, some JS frameworks generated IDs automatically and make maintaining the value of those IDs purposefully obtuse. Likewise, in some extremes cases, the expectation of IDREFs requires generating thousands of DOM modifications which can lead to serious performance problems in the application.
It's be useful to associate related elements using a JavaScript object reference.
Contributor guide
No contributing guide indexed for this repository
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 files, tests, or entry points. Start by reviewing the proposed JavaScript element-reference association against the described IDREF and accessibility use cases; done would require a defined implementation scope and acceptance criteria for the replacement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- accessibility, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100