Closed Bug 2056385 Opened 2 days ago Closed 1 day ago

[wpt-sync] Sync PR 61423 - ContainerTiming: tests for pre-paint attribution tracker

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox155 fixed)

RESOLVED FIXED
155 Branch
Tracking Status
firefox155 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 61423 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/61423
Details from upstream follow.

Jose Dapena Paz <jdapena@igalia.com> wrote:

ContainerTiming: tests for pre-paint attribution tracker

Split out of the pre-paint attribution tracker implementation CL to keep
that change focused on production code.

Adds:

  • Unit tests for the ContainerTimingPaintAttributionTracker and for
    ContainerTiming aggregation/caching under both flag states.
  • pre_paint_tree_walk_test.cc coverage for the container-timing dirty-bit
    propagation and the ShouldInheritContainerTimingRoot cache.
  • display_lock_context_test.cc coverage for the container-timing
    interaction with display locking.
  • container_timing_test_utils.h, shared by blink_unittests and
    blink_perf_tests via unit_test_support.
  • WPTs for container timing roots with containertiming-ignore reporting
    their own paints, plus a virtual test suite running the existing
    container-timing WPTs with ContainerTimingPrepaintTraversal enabled.

All Container Timing Web Platform Tests pass with both the legacy
implementation and the prepaint optimization.

Bug: 489959278
Change-Id: Iaad076cafb821c7807edb739db764b34072ed0bc

Reviewed-on: https://chromium-review.googlesource.com/7979158
WPT-Export-Revision: e580d5e3827e762b5a35d9e6aca43a39c4861dff

CI Results

Ran 0 Firefox configurations based on mozilla-central, and Firefox, Chrome, and Safari on GitHub CI

Total 4 tests and 1 subtests

Status Summary

Firefox

OK : 4
FAIL: 4

Chrome

OK : 4
PASS: 4

Safari

OK : 4
FAIL: 4

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Status: NEW → RESOLVED
Closed: 1 day ago
Resolution: --- → FIXED
Target Milestone: --- → 155 Branch
You need to log in before you can comment on or make changes to this bug.