Closed Bug 1757803 Opened 9 months ago Closed 9 months ago

[wpt-sync] Sync PR 33033 - [FedCM] Make privacy policy url required

Categories

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

task

Tracking

()

RESOLVED FIXED
100 Branch
Tracking Status
firefox100 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

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

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

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

Nicolás Peña Moreno <npm@chromium.org> wrote:

[FedCM] Make privacy policy url required

Currently we allow no privacy policy url to be specified in the client
metadata. This CL changes that by surfacing an error if the JSON parser
returns an empty value for |privacy_policy_url|. Note that currently we
are not sanity checking the strings themselves to ensure the URLs
provided are actually valid URLs, and this CL does not change that. In
order to properly surface the problem about missing privacy policy, we
add a specific console error message. We also add a new value to the
FederatedAuthRequestIssueReason so that a similar message can be
displayed in the Issues panel.

Bug: 1293913
Change-Id: I5dbb6e6a1005db33dccafb7977fb7cced8f871d3
Reviewed-on: https://chromium-review.googlesource.com/3499232
WPT-Export-Revision: 689a9935eeea65249fd0edd1c6f196da181b01b1

PR 33033 applied with additional changes from upstream: a5996ace0256d702602318cd824c816066eb792b
Component: web-platform-tests → DOM: Security
Product: Testing → Core
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Whiteboard: [wptsync downstream][domsecurity-backlog] → [wptsync downstream]
Whiteboard: [wptsync downstream] → [wptsync downstream][domsecurity-backlog]
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/edce89881ec6
[wpt PR 33033] - [FedCM] Make privacy policy url required, a=testonly
Test result changes from PR not available.
Status: NEW → RESOLVED
Closed: 9 months ago
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch
You need to log in before you can comment on or make changes to this bug.