1899707 - New wpt failures in /css/css-contain/content-visibility/content-visibility-auto-state-changed.html

Status: RESOLVED DUPLICATE of bug 1898833

(Core :: Layout, defect)

Description

[Web Platform Test Sync Bot [:wpt-sync] (Matrix: #interop:mozilla.org)]

Syncing wpt PR 46534 found new untriaged test failures in CI

Tests Affected

New Tests That Don't Pass

• /css/css-contain/content-visibility/content-visibility-auto-state-changed.html [wpt.fyi]
  • ContentVisibilityAutoStateChange content attribute test: NOTRUN (Chrome: FAIL, Safari: PASS)

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1899554 lands.

Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.

This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/

If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.

Comment 1

[Daniel Holbert [:dholbert]]

It looks like we already timeout in one of the first parts of this test, and we don't run the subsequent parts (including the part that was added in the PR that's referenced here).

The preexisting timeout is in this section:
ContentVisibilityAutoStateChange fires when relevant element gains content-visibility:auto (oncontentvisibilityautostatechange syntax)

...which corresponds to this element:

<div id=contentattrtest oncontentvisibilityautostatechange="contentattrDidFire()" class=auto></div>

I wonder if we support that "oncontentvisibilityautostatechange" attribute? Searchfox doesn't find any hits for that token, outside of this one WPT test (and its expected-failure annotation):
https://searchfox.org/mozilla-central/search?q=oncontentvisibilityautostatechange&path=

Comment 2

[Daniel Holbert [:dholbert]]

...but really this is just a dupe of bug 1898833, basically (which tracks the preexisting timeout/notrun status for the subtests here).

This new bug was just auto-filed for a new subtest that was added after the timeout-inducing-part-of-the-test. The new subtests is unsurprisingly NOTRUN because we've timed out before we get to it, not because of any new bug identified in the newly added part of the test.