Closed Bug 1853801 Opened 2 years ago Closed 2 years ago

[wpt-sync] Sync PR 42001 - Fix extra rel=match in test reference.

Categories

(Core :: DOM: Core & HTML, task, P4)

task

Tracking

()

RESOLVED FIXED
120 Branch
Tracking Status
firefox120 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

L. David Baron <dbaron@chromium.org> wrote:

Fix extra rel=match in test reference.

rel=match in a reference file does constitute an additional test
assertion, but I think this one was just left by mistake, since it
points to another reference file that has different text.

This equality assertion currently fails across all engines:
https://wpt.fyi/results/html/dom/elements/global-attributes/dir_auto-N-EN-ref.html

Bug: 576815, 1222729
Change-Id: I15bc9746fcd080cbab2f382ba3bef271ab6a627a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4867180
Auto-Submit: David Baron \<dbaron@chromium.org>
Reviewed-by: Di Zhang \<dizhangg@chromium.org>
Commit-Queue: Di Zhang \<dizhangg@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1197221}

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream error]
Whiteboard: [wptsync downstream error] → [wptsync downstream]

CI Results

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

Total 1 tests

Status Summary

Firefox

PASS: 1

Chrome

PASS: 1

Safari

PASS: 1

Links

Gecko CI (Treeherder)
GitHub PR Head
GitHub PR Base

Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2432fd5cfcf3 [wpt PR 42001] - Fix extra rel=match in test reference., a=testonly
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 120 Branch
You need to log in before you can comment on or make changes to this bug.