Closed Bug 1936421 Opened 2 months ago Closed 2 months ago

[wpt-sync] Sync PR 49625 - Implement PaintTimingMixin for element timing

Categories

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

task

Tracking

(firefox135 fixed)

RESOLVED FIXED
135 Branch
Tracking Status
firefox135 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Noam Rosenthal <nrosenthal@chromium.org> wrote:

Implement PaintTimingMixin for element timing

Remove PaintTimingCallbackManager, and instead use the
PaintTiming presentation callback for element-timing and LCP.

For now, only element timing exposes PaintMixin, LCP will be
done in a follow up.

To avoid a big refactor, element timing and LCP are still using
callbacks like before, and MarkPaintTimingInternal integrates
with those.

Bug: 381270287
Change-Id: I65e56ed09713c20b04cfdd6466105aa090db0f3d
Reviewed-on: https://chromium-review.googlesource.com/6063655
WPT-Export-Revision: b433f185a6e22e70abd1ad9efaa1b11e3cd6eb4c

CI Results

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

Total 38 tests and 1 subtests

Status Summary

Firefox

OK : 38
FAIL: 38

Chrome

OK : 38
PASS: 8
FAIL: 30

Safari

OK : 38
FAIL: 38

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/c7e408709530 [wpt PR 49625] - Implement PaintTimingMixin for element timing, a=testonly
Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 135 Branch
You need to log in before you can comment on or make changes to this bug.