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.
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:
Would not emit a new entry.