New wpt failures in /css/css-contain/content-visibility/content-visibility-auto-state-changed.html
Categories
(Core :: Layout, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox130 | --- | fixed |
People
(Reporter: wpt-sync, Assigned: gregp)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-needed, Whiteboard: [wpt], [wptsync upstream])
Attachments
(1 file)
Syncing wpt PR 46479 found new untriaged test failures in CI
Tests Affected
Firefox-only failures
- /css/css-contain/content-visibility/content-visibility-auto-state-changed.html [wpt.fyi]:
SKIP
[Gecko-android-em-7.0-x86_64-lite-qr-opt-geckoview
,Gecko-android-em-7.0-x86_64-qr-debug-geckoview
,Gecko-android-em-7.0-x86_64-qr-opt-geckoview
,Gecko-linux1804-64-qr-debug
,Gecko-linux1804-64-qr-opt
,Gecko-windows11-32-2009-qr-debug
,Gecko-windows11-32-2009-qr-opt
,Gecko-windows11-64-2009-qr-debug
,Gecko-windows11-64-2009-qr-opt
],TIMEOUT
[GitHub
]- ContentVisibilityAutoStateChange fires when relevant element gains
content-visibility:auto
(oncontentvisibilityautostatechange syntax):TIMEOUT
- ContentVisibilityAutoStateChange fires when not relevant element gains
content-visibility:auto
:NOTRUN
- ContentVisibilityAutoStateChange fires when skipped:
NOTRUN
- ContentVisibilityAutoStateChange fires when not skipped:
NOTRUN
- ContentVisibilityAutoStateChange fires when relevant element gains
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1898809 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.
Updated•1 year ago
|
Comment 2•1 year ago
|
||
[Quoting what I put in bug 1899707 (which added another subtest here, which is also NOTRUN because it's after the timeout that's tracked in this bug)]
The 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 at all? 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=
If we don't support that syntax, it would explain pretty trivially why we're timing out when waiting for that callback to fire, I think. :)
Assignee | ||
Comment 3•1 year ago
|
||
Updated•1 year ago
|
Reporter | ||
Comment 5•1 year ago
|
||
Reporter | ||
Updated•1 year ago
|
Comment 6•1 year ago
|
||
Backed out for causing mochitest failures on test_interfaces_secureContext.html
Reporter | ||
Comment 7•1 year ago
|
||
Updated•1 year ago
|
Assignee | ||
Updated•1 year ago
|
Comment 9•1 year ago
|
||
Backed out for causing wpt failures on trusted-types-event-handlers.html
Comment 10•1 year ago
|
||
Reporter | ||
Comment 11•1 year ago
|
||
Assignee | ||
Updated•1 year ago
|
Comment 12•1 year ago
|
||
bugherder |
Reporter | ||
Comment 13•1 year ago
|
||
Reporter | ||
Comment 14•1 year ago
|
||
Assignee | ||
Updated•1 year ago
|
Description
•