Normatively define the “elementtiming” content attribute
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- PR merge metrics
- PR metrics pending
Description
https://wicg.github.io/element-timing/#dom-element-elementtiming defines an elementtiming IDL attribute and states:
The
elementTimingattribute must reflect the element’s "elementtiming" content attribute.
…but nowhere does the spec actually define the elementtiming content attribute.
Even if sufficient implementor interest for the feature has not be demonstrated yet, a PR with the patch for adding it to the HTML spec can (should) be opened.
The patch should provide the normal details the HTML spec defines for other content attributes, including datatype/ microsyntax (allowed values) for the attributes, as well as stating which elements are allowed to have the attribute, etc.
cc @npm1, @yoavweiss
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
Start with the linked Element Timing specification definition and the HTML Standard's existing content-attribute definitions. Determine the allowed elements, datatype, and microsyntax for the elementtiming content attribute; done means those normative details are defined and its relationship to the elementTiming IDL attribute is clear.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100