Closed Bug 1984620 Opened 7 months ago Closed 7 months ago

[wpt-sync] Sync PR 54456 - ContainerTiming: add containerTimingNesting attribute support

Categories

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

task

Tracking

(firefox144 fixed)

RESOLVED FIXED
144 Branch
Tracking Status
firefox144 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

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

ContainerTiming: add containerTimingNesting attribute support

In a hierarchy of several container timing roots (elements with the
containertiming flag), paint information is not propagated to the
parent roots.

With this change, we introduce a nesting policy, that can be
specified with the attribute "containertiming-nesting". This can be
added to nodes with "containertiming" attribute.

The default mode is non propagating (painting of a container timing
tree is not forwarded to other container tree roots the node may be
included in).

But we support two additional modes that are passed as parameters of
"containertiming-nesting":

  • "transparent": the paints are forwarded to next container tree root
    as they are.
  • "shadowed": the paints are forwarded, but replacing the specific
    element with the container tree root.

Additional WPT tests provided for nesting, and for its interaction with
containertiming-ignore.

Explainer: https://github.com/bloomberg/container-timing/blob/main/README.md
Chromestatus: https://chromestatus.com/feature/5110962817073152
I2P: https://groups.google.com/a/chromium.org/g/blink-dev/c/J-WxY0w7bNk/m/VkqnomK-CAAJ

Ticket for nesting policy specification discussion:
https://github.com/bloomberg/container-timing/issues/3

Bug: 382422286
Change-Id: I0c932823a9e72ca87558bbf85ad893c5e3696d25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6270778
Reviewed-by: Joey Arhar \<jarhar@chromium.org>
Commit-Queue: José Dapena Paz \<jdapena@igalia.com>
Cr-Commit-Position: refs/heads/main@{#1504890}

CI Results

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

Total 10 tests and 1 subtests

Status Summary

Firefox

OK : 10
FAIL: 10

Chrome

OK : 10
PASS: 5
FAIL: 5

Safari

OK : 10
FAIL: 10

Links

GitHub PR Head
GitHub PR Base

Details

New Tests That Don't Pass

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