Following our prior art considerations <https://docs.google.com/document/d/1RukWSQJqA_RvPYs7KVU9P3HSHq5X5o31OrNyYum0C2A/edit?resourcekey=0-US0u-1gfC1yEynPeNptlwA&tab=t.0#heading=h.xejc1hvpku7d> for the payment link type proposal, we've decided to rename the `payment` keyword to `facilitated-payment` in the `rel` attribute. This is based on the conflict of microformat's rel='payment' proposal <https://microformats.org/wiki/rel-payment#Practical_examples_of_rel=%22payment%22>, and the existing defined `payment` keyword in IANA registry <https://www.iana.org/assignments/link-relations/link-relations.xhtml>.
On Fri, Nov 15, 2024 at 3:31 PM Junhui He <junhu...@google.com> wrote: > External review requested: > > TAG design review: https://github.com/w3ctag/design-reviews/issues/1015 > WebKit standard position review: > https://github.com/WebKit/standards-positions/issues/428 > Mozilla standard position review: > https://github.com/mozilla/standards-positions/issues/1112 > > On Tue, Oct 29, 2024 at 1:50 PM Junhui He <junhu...@google.com> wrote: > >> The paymentlink repo including explainer is moved to WICG at >> https://github.com/WICG/paymentlink. >> >> On Mon, May 20, 2024 at 3:39 PM Junhui He <junhu...@google.com> wrote: >> >>> The public version of HTML payment link design doc is available at >>> bit.ly/html-payment-link-dd. >>> >>> On Wed, May 8, 2024 at 11:57 AM Junhui He <junhu...@google.com> wrote: >>> >>>> WICG proposal was sent out at >>>> https://github.com/WICG/proposals/issues/150 >>>> >>>> On Wed, May 8, 2024 at 11:03 AM Junhui He <junhu...@google.com> wrote: >>>> >>>>> Contact emailsaneesh...@google.com, junhu...@google.com >>>>> >>>>> Explainer >>>>> https://github.com/aneeshali/paymentlink/blob/main/docs/explainer.md >>>>> >>>>> Summary >>>>> >>>>> Adds support for <link rel="payment" href="..."> as a hint that the >>>>> browser should notify registered payment clients about a pending push >>>>> payment. When Blink encounters this HTML element, then it will send a >>>>> message to the browser to display the user's interface to ask the user if >>>>> they would like to invoke Google Pay to assist payments on this page. >>>>> >>>>> Blink componentBlink>Payments >>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPayments> >>>>> >>>>> Motivation >>>>> >>>>> This feature lets the browser assist users in push-based payment flows >>>>> by facilitating the transfer of payment information between the payment >>>>> provider (on the payee side) and the payment client (on the payer side). >>>>> The feature lays the foundation for payment integrators in streamlining >>>>> push-based payment flows, towards a consistent and low-friction user >>>>> experience. >>>>> >>>>> Risks >>>>> Interoperability and Compatibility >>>>> >>>>> We're not aware that anybody else uses payment link <link >>>>> rel="payment">. >>>>> >>>>> *Gecko*: No signal >>>>> >>>>> *WebKit*: No signal >>>>> >>>>> *Web developers*: No signals >>>>> >>>>> WebView application risks >>>>> >>>>> Does this intent deprecate or change behavior of existing APIs, such >>>>> that it has potentially high risk for Android WebView-based applications? >>>>> >>>>> None >>>>> >>>>> Flag name on chrome://flags#enable-payment-link-detection >>>>> >>>>> Finch feature name"EnablePaymentLinkDetection" >>>>> >>>>> Requires code in //chrome?True - Detection of the payment link does >>>>> not need coding //chrome, but code in //chrome will eventually be required >>>>> to invoke Google Pay APIs. >>>>> >>>>> Tracking bughttps://crbug.com/1477049 >>>>> >>>>> Estimated milestones >>>>> >>>>> M132 >>>>> >>>>> Link to entry on the Chrome Platform Status >>>>> https://chromestatus.com/feature/5198846820352000?gate=5076188191522816 >>>>> >>>>> -- 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+unsubscr...@chromium.org. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAAgNxUvZpFZxUcijZzyvPb3xV9PeawOTkWseLc9wc8BfSHO9AQ%40mail.gmail.com.
