Repository navigation
Conversation
The spec never said when handle element painted runs. Run it for each image and text element on its first contentful paint, and again if the element is removed or moved and then painted again. See w3c#72.
beckysiegel
pushed a commit
to chromium/chromium
that referenced
this pull request
Nov 5, 2026
Test removing the containertiming attribute, changing the identifier, and removing, reinserting or moving the root, as discussed in [1]. Reinsert and move fail: the root keeps its painted region, so no entry is emitted. moveBefore() follows [2], and reinserted content being reported again follows [3]. Adds observeContainerEntries() for tests mutating the DOM between paints. [1] w3c/container-timing#60 [2] w3c/container-timing#86 [3] w3c/container-timing#84 Change-Id: Ifb155cd30c1925f068901f8dc22450e9add5338f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8677581 Reviewed-by: Scott Haseley <shaseley@chromium.org> Commit-Queue: José Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/main@{#1736289}
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Nov 5, 2026
Test removing the containertiming attribute, changing the identifier, and removing, reinserting or moving the root, as discussed in [1]. Reinsert and move fail: the root keeps its painted region, so no entry is emitted. moveBefore() follows [2], and reinserted content being reported again follows [3]. Adds observeContainerEntries() for tests mutating the DOM between paints. [1] w3c/container-timing#60 [2] w3c/container-timing#86 [3] w3c/container-timing#84 Change-Id: Ifb155cd30c1925f068901f8dc22450e9add5338f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8677581 Reviewed-by: Scott Haseley <shaseley@chromium.org> Commit-Queue: José Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/main@{#1736289}
chromium-wpt-export-bot
pushed a commit
to web-platform-tests/wpt
that referenced
this pull request
Nov 5, 2026
Test removing the containertiming attribute, changing the identifier, and removing, reinserting or moving the root, as discussed in [1]. Reinsert and move fail: the root keeps its painted region, so no entry is emitted. moveBefore() follows [2], and reinserted content being reported again follows [3]. Adds observeContainerEntries() for tests mutating the DOM between paints. [1] w3c/container-timing#60 [2] w3c/container-timing#86 [3] w3c/container-timing#84 Change-Id: Ifb155cd30c1925f068901f8dc22450e9add5338f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8677581 Reviewed-by: Scott Haseley <shaseley@chromium.org> Commit-Queue: José Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/main@{#1736289}
lando-worker Bot
pushed a commit
to mozilla-firefox/firefox
that referenced
this pull request
Nov 20, 2026
…ute or the container root, a=testonly Automatic update from web-platform-tests ContainerTiming WPT: removing the attribute or the container root Test removing the containertiming attribute, changing the identifier, and removing, reinserting or moving the root, as discussed in [1]. Reinsert and move fail: the root keeps its painted region, so no entry is emitted. moveBefore() follows [2], and reinserted content being reported again follows [3]. Adds observeContainerEntries() for tests mutating the DOM between paints. [1] w3c/container-timing#60 [2] w3c/container-timing#86 [3] w3c/container-timing#84 Change-Id: Ifb155cd30c1925f068901f8dc22450e9add5338f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8677581 Reviewed-by: Scott Haseley <shaseley@chromium.org> Commit-Queue: José Dapena Paz <jdapena@igalia.com> Cr-Commit-Position: refs/heads/main@{#1736289} -- wpt-commits: d7cc0cd6198afa1c9aefe353bedfff6de70e91ae wpt-pr: 64808
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The spec never said when handle element painted runs. Run it for each image and text element on its first contentful paint, and again if the element is removed or moved and then painted again.
See #72.
Preview | Diff