Should elements only report paints once to Container Timing?
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 72
- Forks
- 10
- Avg merge
- 9d 15h
- Merged PRs (30d)
- 3
Description
In Chromium the behavior is inherited from ElementTiming (and sharing some logic with ICP/LCP). An element will only report one time. For images, it is when the load is complete and we get the paint for that. For text it only reports once for the text aggregator.
LCP defines that explicitely https://www.w3.org/TR/largest-contentful-paint/#sec-report-largest-contentful-paint
ICP has some open questions about what to do here.
As Container Timing is inspired on the idea of LCP, we should likely explicitely state in the specification that the elements will only report once, in the same way LCP does (or refer somehow to that part of LCP specification).
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 by reading the Container Timing specification and compare its reporting behavior with the linked Largest Contentful Paint reporting rule. Clarify in the specification that elements report only once, or add an appropriate reference to the LCP requirement; done means the rule is explicit and consistent with the intended image and text behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100