Open Bug 1911791 Opened 1 year ago Updated 1 year ago

New wpt failures in /css/css-pseudo/parsing/marker-supported-properties-in-animation.html

Categories

(Core :: Layout: Generated Content, Lists, and Counters, defect)

Product:
Core
Component:
Layout: Generated Content, Lists, and Counters
Type:
defect

Tracking

()

People

(Reporter: wpt-sync, Unassigned)

References

(Depends on 2 open bugs)

Details

(Whiteboard: [wpt])

Syncing wpt PR 47454 found new untriaged test failures in CI

Tests Affected

Firefox-only failures

  • /css/css-pseudo/parsing/marker-supported-properties-in-animation.html [wpt.fyi]
    • Animation of text-emphasis in ::marker: FAIL
    • Animation of text-emphasis-color in ::marker: FAIL
    • Animation of text-emphasis-position in ::marker: FAIL
    • Animation of text-emphasis-style in ::marker: FAIL
    • Transition of text-emphasis in ::marker: FAIL
    • Transition of text-emphasis-color in ::marker: FAIL
    • Transition of text-emphasis-position in ::marker: FAIL
    • Transition of text-emphasis-style in ::marker: FAIL

CI Results

Gecko CI (Treeherder)
GitHub PR Head

Notes

These updates will be on mozilla-central once bug 1911585 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.

Weird that wpt-bot is thinking these text-emphasis failures are new. They're not the new thing that was just added to this WPT test; the text-emphasis subtests were added back in https://github.com/web-platform-tests/wpt/pull/25427

It looks like we have bug 1663539 on that old PR, and these tests were noted as failing at that point in bug 1663539 comment 3. Though at that point, the failures were for all browsers.

Anyway: triaging as S3.

Severity: -- → S3
Depends on: 1663539, 1673735
You need to log in before you can comment on or make changes to this bug.