WICG / WICG/container-timing

WPT: Add test for text updates

Open
#49 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

We've seen that text updates don't count as new entries for container timing, this is consistent with LCP and element-timing
This is intentional and we will want to add a test to make sure this is being followed by all browsers.

For example:

<div containertiming>
<p>test</p>
</div>
const p = document.querySelector('[containertiming] p');
p.textContent = "some longer text";

Would not emit a new entry.

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

No file or test path is identified in the issue. Start by locating the existing Container Timing web-platform tests and their test entry points, then add coverage for changing the paragraph text inside a containertiming element. Done means the text update does not produce a new entry across browsers.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, javascript
Domain
testing, web-dev
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.