WICG / WICG/container-timing

Is there any mechanism for observing that the whole container has "finished" painting?

Open
#40 7 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

needs discussion
Dominant language
Bikeshed
Stars
72
Forks
10
Avg merge
9d 15h
Merged PRs (30d)
3

Description

I understand that with Container Timing there are various issue that may make it impossible to know that a Container has fully finished painting:

  • Some content may be below-the-fold, and user may scroll
  • Some content may be offscreen, transparent, or obscured in ways that skip paint, but may move.

Etc.

But what about simple cases like: a container timing attribute applied to a single element leaf node (aka the element timing use case)?

Or for simple containers, where all potentially-contentful leaf nodes are known, and have all already reported contentful paints?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the Container Timing cases described in the issue, especially a leaf element and a simple container whose contentful paints have all reported. Define what a reliable “finished” signal would mean despite below-the-fold, offscreen, transparent, or obscured content; done when the proposed mechanism and its limits are clear.

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
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.