Element Timings and below-the-fold content report arbitrary timings and not useful intersectionRect.
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 61
- Forks
- 19
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 1
Description
If an element is scrolled out of view before it has finished loading, its intersectionRect will be 0. It would be useful to have the intersectionRect be based on the initial viewport (when the element was added to the DOM) instead of the current viewport at render time. This would enable collecting timings for elements that were in the initial viewport based on its intersectionRect. The comparison can still be done after the element has rendered, but the element would be compared against a representation of the initial viewport.
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 reviewing the Element Timing proposal and the issue's description of intersectionRect, initial viewport state, and below-the-fold elements. Define the intended initial-viewport semantics and update the proposal so the behavior and completion criteria are explicit.
Written by the indexing model from the issue text.
Assessment
- Domain
- performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100