Closed Bug 1894641 Opened 5 months ago Closed 5 months ago

[wpt-sync] Sync PR 46016 - Fix the "or" condition WPT

Categories

(Core :: DOM: Service Workers, task, P4)

Product:
Core
Component:
DOM: Service Workers
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
127 Branch
Tracking Flags:
Tracking Status
firefox127 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Yoshisato Yanagisawa <yyanagisawa@chromium.org> wrote:

Fix the "or" condition WPT

In the previous WPT, it hits Step 7.1, and always gets addRoutes()
failure. The "or" condition and other conditions cannot be defined at
the same time.
https://w3c.github.io/ServiceWorker/#verify-router-rule-algorithm

Since we wanted to check the depth of the "or" condition in the WPT, the
condition should not hit Step 7.1.

Change-Id: Ia05d398ed64ec93c0485bf3a52d7131d1a27cfb8
Bug: 40284745
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5508558
Reviewed-by: Shunya Shishido \<sisidovski@chromium.org>
Reviewed-by: Minoru Chikamune \<chikamune@chromium.org>
Commit-Queue: Yoshisato Yanagisawa \<yyanagisawa@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1295310}

PR 46016 applied with additional changes from upstream: 500f11b59f5417c9b29080d27ef1fd47f4b1495b, 3a9b4373063ea7eaa68bbb68a711634ed169c665, 0dfe7506f172ba5e543c9becbc07b6ab5747d4fd
Component: web-platform-tests → DOM: Service Workers
Product: Testing → Core
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Test result changes from PR not available.
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/ec44cbd8c7b0 [wpt PR 46016] - Fix the "or" condition WPT, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/ec44cbd8c7b0

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