Re: CFC: addition of "protocol_handlers" to web manifest

Are "deep-links" also a part of the Web Manifest?

Since PaymentRequest doesn't support a "companion API" for payment credential enrollment, "deep-links" have become the de-facto standard for Web2Native integration, also for payments.

Thanx,
Anders

On 2021-07-22 9:49, Marcos Caceres wrote:
> Hi Working Group Folks - specially Web Manifest Implementers,
> 
> Diego Gonzalez-Zuniga (Microsoft) and co. are seeking feedback on the addition of a "protocol_handlers" member to the Web Manifest.
> 
> Feature summary: "Installed Web applications can greatly benefit from being registered as a handler for protocols (schemes) on the platform they are running on. This feature creates a more immersive experience where the application gains better cross-app integration.
> 
> For example, an installed Web app could be able to ‘open’ mailto:// links. This can be requested for both existing and custom protocols. To do so, a new member in the manifest file (`protocol-handlers`) allows developers to define the associations that the app can handle upon being installed, all pending approval by the user the first time that that particular protocol is invoked from within an installed web application."
> 
> This is a Call for Comment seeking feedback for inclusion of the proposal into Web Manifest. The corresponding pull request is at [2]. Please indicate your support or objection for its inclusion at [2]. A preview of the proposed spec change is at [1], and is currently implemented behind a flag in Microsoft Edge (details below).
> 
> If you have Edge and want to see it working, you can enable:
> 
> edge://flags/#enable-desktop-pwas-protocol-handling
> 
> And you can try it out at: https://protocol-handler-link.glitch.me
> 
> Thanks!
> 
> Marcos
> Web Apps WG Co-Chair
> 
> [1] https://pr-preview.s3.amazonaws.com/w3c/manifest/972/2db851c...ec620b6.html#protocol_handlers-member
> [2] https://github.com/w3c/manifest/pull/972
>

Received on Thursday, 22 July 2021 08:01:42 UTC