Closed Bug 1756232 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 32907 - [FedCM] Fix relative paths in fedcm.json

Categories

(Core :: DOM: Security, task, P4)

Product:
Core
Component:
DOM: Security
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
100 Branch
Tracking Flags:
Tracking Status
firefox100 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream][domsecurity-backlog])

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

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

Christian Biesinger <cbiesinger@chromium.org> wrote:

[FedCM] Fix relative paths in fedcm.json

The current code effectively resolves the paths relative to the
root, which is not correct. Just use provider_ as-is instead of
going through origin (which removes paths).

R=yigu@chromium.org

Change-Id: I383afa3b85511e23b1cd5ef25de867c0c805e3b3
Reviewed-on: https://chromium-review.googlesource.com/3472523
WPT-Export-Revision: f0f15c1bac9ce792d5814e2241b201afe249697d

PR 32907 applied with additional changes from upstream: a5996ace0256d702602318cd824c816066eb792b
Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0b565915674e [wpt PR 32907] - [FedCM] Fix relative paths in fedcm.json, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/0b565915674e

Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox100: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.