Closed Bug 1828155 Opened 2 years ago Closed 10 months ago

[wpt-sync] Sync PR 39547 - [payto] Add "payto" to custom protocol allowlist.

Categories

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

task

Tracking

()

RESOLVED INVALID

People

(Reporter: wpt-sync, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

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

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

Rastislav <rastislav.vasicka@codetech.cc> wrote:

[payto] Add "payto" to custom protocol allowlist.

The Payto scheme is described in RFC 8905 but not adapted in
the safe listed scheme list.
Supporting this RFC Independent Submission (ISSN: 2070-1721)
it will enable various transfer methods.

The resulting behavior is:

  • If a system handler for the payto scheme exists, that system handler
    takes priority over registerProtocolHandler. Hence
    registerProtocolHandler call will succeed but the registered handler
    does not recieve navigations to payto URLs.

  • When native PAYTO support is enabled (e.g. via a command-line option
    prior to the code going away), registration of custom handlers for
    payto will succeed.

  • When native PAYTO support is disabled (the default in Chromium at this
    point) behavior is as stated.

Bug: 1432881

Change-Id: Iaacd24bc29fe2442cc09157b34764ddc29e1ca77
Reviewed-on: https://chromium-review.googlesource.com/4427815
WPT-Export-Revision: 232e44f1e5b1949959dd26909ca53adb5d66b3b8

Component: web-platform-tests → DOM: Core & HTML
Product: Testing → Core
Status: NEW → RESOLVED
Closed: 10 months ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.