Allow Navigator.registerProtocolHandler to register "payto"

[Rastislav Vašička]

Explainer

A unified URI scheme for all payment target types allows applications to offer user interactions with URIs that represent payment targets, simplifying the introduction of new payment systems and applications.

Specification

RFC 8905

Summary

Add "payto" to the list of protocols available for registration via registerProtocolHandler(). The Payto scheme is described in RFC 8905 but not adapted in the safelisted scheme list. To support this standard it will be great to adapt it.

Blink component

Blink>HTML>CustomHandlers

Risks

Interoperability and Compatibility

None

The implementation gives precedence to native protocol handlers before consulting sites registered via registerProtcolHandler.

Gecko: No signal

WebKit: No signal

Web developers: No signals

[Mike Taylor]

Hi Rastislav,

Can you clarify - do you intend to prototype this? Do you have a bug or CL where you're doing the work?

thanks,
Mike

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/44b54a21-2f87-4aca-8c06-6a76a93daac8n%40chromium.org.

[Rastislav Vašička]

Sure, Mike.

As the protocol is defined in RFC 8905, it may be implemented in the system.

The bug is located here: https://bugs.chromium.org/p/chromium/issues/detail?id=1432881

Prototype and PR are in progress.

[Mike Taylor]

Got it - we'll treat this as an Intent to Prototype then (typically an Intent starts with "Intent to Prototype" (or Experiment, Ship, etc.).

You'll want to create a chromestatus.com entry with the proposed new feature (see https://www.chromium.org/blink/launching-features/#launch-process - that explains how to get access to create a new feature, if you don't already have it).

I think it would also be useful to flesh out the Explainer a bit, focusing on the concrete use cases you're trying to enable.

thanks,
Mike

[Dave Tapuska]

I feel the chromestatus is a bit misleading on the Mozilla position. It indicates "Worth Prototyping" with a link to the Mozilla positions github issue. But no one from Mozilla has indicated a position.

dave.

On Thu, Apr 13, 2023 at 3:05 PM Rastislav Vašička <rastisla...@codetech.cc> wrote:

Thank you. Created https://chromestatus.com/feature/5199727026503680

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/60c4c259-9d01-41b1-ab03-f2956d88ffc2n%40chromium.org.

[Mike Taylor]

Agree - I've changed it to "Under Consideration" until they respond with an official position. Thanks for pointing that out, Dave.

[Rastislav Vašička]

Thank you. I will check with Mozilla.

Updated here: https://chromium-review.googlesource.com/c/chromium/src/+/4428674