[blink-dev] Intent to Ship: Payment handler minimal header UX

*Contact emails*nbur...@chromium.org *Explainer* https://crbug.com/1385136 - see comment 14 for screenshot *Specification* Not applicable *Design docs* (Google internal only, sorry): https://docs.google.com/document/d/1hCIzyBALzpFPuHQ_xCNvIpSrMThq8PA6Qgi0M2iF9vk/edit?resourcekey=0-VMUV90L2bb2Oql

[blink-dev] Intent to Experiment: Secure Payment Confirmation - Opt-Out Support

*Contact emails* smcgr...@chromium.org, rous...@chromium.org *Explainer* https://github.com/w3c/secure-payment-confirmation/issues/172 *Specification* https://w3c.github.io/secure-payment-confirmation *Summary* Adds an 'opt-out' flow to Secure Payment Confirmation. When the (optional) input flag

[blink-dev] Intent to Prototype: PaymentHandler - connect-src CSP policy

Contact emailssmcgr...@chromium.org, rous...@chromium.org Specificationhttps://www.w3.org/TR/payment-method-manifest/#processing-model Summary Deprecate the ability for PaymentHandler to bypass the connect-src CSP policy when fetching the manifest. After this deprecation, a site's connect-src CS

[blink-dev] Intent to Deprecate and Remove: PaymentInstruments

Contact emailsrous...@chromium.org, smcgr...@chromium.org Summary PaymentInstruments is the Web API that backs non-JIT install of payment apps (see https://w3c.github.io/payment-handler/). It was designed with the assumption th

Re: [blink-dev] Intent to Deprecate and Remove: PaymentInstruments

e contexts? > And do we know how these few sites who are using the API... are using the > API? Does any real-world usage show up in HTTP Archive? > > thanks, > Mike > > On 9/14/22 8:55 AM, Chris Harrelson wrote: > > LGTM1 > > On Wed, Sep 14, 2022 at 8:05

Re: [blink-dev] Intent to Deprecate and Remove: PaymentInstruments

are limited in impact and do not affect overall site functionality. On Tue, Sep 20, 2022 at 5:20 AM Yoav Weiss wrote: > > > On Thu, Sep 15, 2022 at 9:03 PM Rouslan Solomakhin > wrote: > >> Hi Mike, >> >> > do we have any reason to believe there are consumers of

Re: [blink-dev] Intent to experiment: Deprecate and remove merchant identity in "canmakepayment"

LGTM to run Origin Trial removal 108-110 M108 is upon us. We intend to start the origin trial shortly. On Wednesday, April 20, 2022 at 12:03:22 PM UTC-4 Yoav Weiss wrote: > LGTM to run Origin Trial removal 108-110 > > On Wednesday, April 20, 2022 at 4:27:10 PM UTC+2 Rouslan Solomakhin

[blink-dev] Intent to Experiment: Web Payment API - connect-src CSP policy

Contact emailssmcgr...@chromium.org, rous...@chromium.org Specificationhttps://www.w3.org/TR/payment-method-manifest/#processing-model Summary Deprecate the ability for Web Payment API to bypass the connect-src CSP policy when fetching the manifest. After this deprecation, a site's connect-src C

Re: [blink-dev] Intent to Deprecate and Remove: PaymentInstruments

ng? > > On Tue, Sep 20, 2022 at 4:26 PM Rouslan Solomakhin > wrote: > >> > Would we expect those uses to break? Are they feature detecting the API >> before using it? >> >> Partially (for both questions!). In examining the site logic we have >> found t

Re: [blink-dev] Intent to Experiment: Web Payment API - connect-src CSP policy

to get properties currently using PaymentHandler to > experiment with this and see if there's breakage? Should we initially ship > a "report only" mode that would help all properties know that CSP errors > may be happening soon? > > On Tue, Sep 20, 2022 at 6:20 PM Rouslan Sol

Re: [blink-dev] Intent to Deprecate and Remove: PaymentInstruments

; environments where telemetry disabled. > > On 9/21/22 9:10 AM, Stephen Mcgruer wrote: > > (remove in M108, to be clear - just restating from the Chromestatus entry > as Yoav asked about the timeline) > > On Wed, Sept 21, 2022, 9:00 a.m. Rouslan Solomakhin > wrote: > >&g

[blink-dev] Intent to deprecate and remove: connect-src CSP bypass in Web Payment API

Contact emailssmcgr...@chromium.org, rous...@chromium.org Specification https://www.w3.org/TR/payment-method-manifest/#processing-model Summary Deprecate the ability for Web Payment API to bypass the connect-src CSP policy when fetching the manifest. After this deprecation, a site's connect-src

Re: [blink-dev] Intent to Experiment: Web Payment API - connect-src CSP policy

>> necessary for anyone to opt out for a few milestones. >> >> Thoughts Yoav? >> >> On Wed, Sept 21, 2022, 9:06 a.m. Rouslan Solomakhin >> wrote: >> >>> > So is the plan to get properties currently using PaymentHandler to >>> experiment w

Re: [blink-dev] Intent to deprecate and remove: connect-src CSP bypass in Web Payment API

Hi, Are there remaining questions for me to answer? (Or maybe the tools are not picking up this intent everywhere...) -- waiting on the last LG 😆 Cheers, Rouslan On Monday, September 26, 2022 at 3:01:18 AM UTC-4 mkwst via Chromestatus wrote: > LGTM2. > -- You received this message because y

Re: [blink-dev] Intent to experiment: Deprecate and remove merchant identity in "canmakepayment"

dData.length > 0) {} if (evt.modifiers && evt.modifiers.length > 0) {} Cheers, Rouslan On Tuesday, September 20, 2022 at 11:06:03 AM UTC-4 Rouslan Solomakhin wrote: > > Chrome is reaching out to the known partners that may be depending on > these fields. > > We have reached

Re: [blink-dev] Intent to experiment: Deprecate and remove merchant identity in "canmakepayment"

using >>> PaymentHandler do not utilize these fields, however we are including it as >>> a safe-guard. >>> >>> No developer signed up to the current Origin Trial, unfortunately >>> (possibly because there is no impact), so we have no data from that. >>>

Re: [blink-dev] Intent to experiment: Deprecate and remove merchant identity in "canmakepayment"

, but I'll try pinging a couple others. >> >> Rick >> >> On Mon, Dec 19, 2022 at 10:49 AM Rouslan Solomakhin >> wrote: >> >>> Hi, >>> >>> Just to make sure, do we have the approval to ship the removal in M111 >>> (together

Re: [blink-dev] Intent to experiment: Deprecate and remove merchant identity in "canmakepayment"

Hey... no worries! The lesson here is to use a new thread next time :-D Happy Holidays! 🎄 ☃️ On Mon, Dec 19, 2022 at 2:36 PM Rick Byers wrote: > SGTM, thanks Rouslan! And sorry again for this thread dropping off API > owner radar. > > On Mon, Dec 19, 2022 at 2:01 PM Rousla

Re: [blink-dev] Intent to Deprecate: The "basic-card" method of PaymentRequest API

> a deprecation period before removal isn't an unreasonable path forward. WDYT That sounds reasonable to us. We are planning a blog post, too, by the way. (Responding on behalf of Stephen and Max because they happen to be both OOO today.) On Thu, Sep 9, 2021 at 2:57 PM Mike West wrote: > Given

Re: [blink-dev] Intent to Deprecate: The "basic-card" method of PaymentRequest API

Sure, let's do 4 milestones. We can put the deprecation message in the developer console in M96 and perform the removal in M100. On Thu, Sep 9, 2021 at 3:26 PM Mike West wrote: > Ok. Does ~4-5 milestones (M100-101 sound good to you?) > > -mike > > > On Thu, Sep 9,

Re: [blink-dev] Intent to Deprecate: The "basic-card" method of PaymentRequest API

sure that > the API's canonical documentation points people in the right direction. > > On Thu, Sep 9, 2021 at 9:28 PM Rouslan Solomakhin > wrote: > >> Sure, let's do 4 milestones. We can put the deprecation message in the >> developer console in M96 and perfo

Re: [blink-dev] Intent to Deprecate: The "basic-card" method of PaymentRequest API

> > On Thu, Sep 16, 2021 at 8:03 PM Daniel Bratell > wrote: > >> Good, because if not, I think it will leave the standard in a strange >> mess where a majority of the documentation will use constructs that no >> longer exists and that will make everyone unhappy. >&

Re: [blink-dev] Intent to Deprecate: The "basic-card" method of PaymentRequest API

- web.dev: >>>>>>>>>> - Eiji is updating web.dev with a PR >>>>>>>>>> <https://github.com/GoogleChrome/web.dev/pull/6203> ( >>>>>>>>>> preview >>

[blink-dev] Intent to Extend Experiment: Digital Goods API

Hello blink-dev, We would like to extend the experiment by two milestones to end in M101 (inclusively), instead of the current origin trial end of M99. Reason this experiment is being extended The motivation is twofold. 1. We need more time to collect feedback from the experimental partners.

[blink-dev] Re: Intent to Extend Experiment: Digital Goods API

uot;intent to extend the experiment" email. Cheers, Rouslan On Sun, Jan 23, 2022 at 8:17 PM Glen Robertson wrote: > This is an intent to extend "Digital Goods API v2.0" not "Digital Goods > API" (they are separate experiments). > > On Fri, 21 Jan 2022 at

[blink-dev] Intent to Prototype: Digital Goods API v2.1

Contact emails rous...@chromium.org, glen...@chromium.org Explainer https://github.com/WICG/digital-goods/blob/main/explainer.md#api-v21 Summary We are implementing behind a flag a non-breaking addition to the existing Digital Goods API. This change: - Adds to DigitalGoodsService: -

[blink-dev] Intent to Ship: Digital Goods API v2.0

Contact emails mgi...@chromium.org, rous...@chromium.org, glen...@chromium.org Explainer https://github.com/WICG/digital-goods/blob/main/explainer.md Spec https://wicg.github.io/digital-goods/ - Currently being reviewed by a spec mentor, so some details may change (hopefully, only formatting).

Re: [blink-dev] Intent to Ship: Digital Goods API v2.0

stores >> <https://github.com/w3ctag/design-reviews/issues/571#issuecomment-861188412> >> implementing this API as well in the future. >> >> >> >>> >>> Also there's been an update on the TAG about the plan of shipping this >>> API

Re: [blink-dev] Intent to Ship: Digital Goods API v2.0

M Manuel Rego Casasnovas wrote: > > > On 02/02/2022 16:51, Rouslan Solomakhin wrote: > >> Rouslan, it looks to me like the API is designed to support multiple > > stores, right? > >> For example if Samsung decided that they wanted to support connecting > &

Re: [blink-dev] Intent to Ship: Digital Goods API v2.0

Feb 3, 2022 at 11:45 AM Rouslan Solomakhin > wrote: > >> > There are lots of stores, and also several browsers based on >> > Chromium. Have we talked to them? Is anyone interested in >> > adding support for this? >> >> Yes, we have talked to the other

[blink-dev] Intent to Ship: Digital Goods API 2.1

Contact emails glen...@chromium.org, rous...@chromium.org Explainer https://github.com/WICG/digital-goods/blob/main/explainer.md#api-v21 Specification https://wicg.github.io/digital-goods/ Difference between 2.0 and 2.1

Re: [blink-dev] Re: Intent to Ship: Digital Goods API 2.1

have recycled the chromestatus >> entry.. /cc +Jason Robbins >> >> On Mon, Apr 11, 2022 at 7:55 PM 'Rouslan Solomakhin' via blink-dev < >> blink-dev@chromium.org> wrote: >> >>> Yep, a few additional API methods and fields. >>> >>&

Re: [blink-dev] Intent to Ship: Digital Goods API 2.1

On Fri, Apr 15, 2022 at 9:44 AM Mike Taylor wrote: > On 4/15/22 12:31 AM, Yoav Weiss wrote: > > On Mon, Apr 11, 2022 at 4:45 PM Rouslan Solomakhin > wrote: > >> Contact emails >> >> glen...@chromium.org, rous...@chromium.org >> >> Explainer >>

Re: [blink-dev] Intent to experiment: Deprecate and remove merchant identity in "canmakepayment"

; On Mon, Apr 18, 2022 at 5:49 PM 'Rouslan Solomakhin' via blink-dev < > blink-dev@chromium.org> wrote: > >> Contact emailsrous...@chromium.org >> >> Specificationhttps://w3c.github.io/payment-handler/ >> >> Summary >> >> This is an

Re: [blink-dev] Re: Intent to Ship: PaymentRequest on WebView

m/a/chromium.org/g/blink-dev/c/p1DYoxHlkKg/m/rBqBMGbFCgAJ > > LGTM1 to ship to WebView as well with the restriction you outlined. Please > also start the rest of the reviews (WP Security, Enterprise, Testing). > > > > On Friday, February 28, 2025 at 3:06:33 PM UTC-5

[blink-dev] Intent to Ship: PaymentRequest on WebView

Contact emailsrous...@chromium.org Specificationhttps://w3c.github.io/payment-request/ Documentationhttps://web.dev/explore/payments (WebView-specific documentation will follow.) Summary PaymentRequest is an API that allo

[blink-dev] Re: Intent to Ship: PaymentRequest on WebView

st: > https://groups.google.com/a/chromium.org/g/blink-dev/c/p1DYoxHlkKg/m/rBqBMGbFCgAJ > > LGTM1 to ship to WebView as well with the restriction you outlined. Please > also start the rest of the reviews (WP Security, Enterprise, Testing). > > > > On Friday, February 28, 2025 at

Re: [blink-dev] Intent to Ship: Digital Goods API 2.1

gt; LGTM3 > > On Fri, Apr 15, 2022, 18:20 Rouslan Solomakhin > wrote: > >> >> >> On Fri, Apr 15, 2022 at 9:44 AM Mike Taylor wrote: >> >>> On 4/15/22 12:31 AM, Yoav Weiss wrote: >>> >>> On Mon, Apr 11, 2022 at 4:45 PM Rouslan Solomakhin

[blink-dev] Re: Intent to Ship: Digital Goods API 2.1

Yep, a few additional API methods and fields. On Monday, April 11, 2022 at 1:52:16 PM UTC-4 Joe Medley wrote: > So this is different from what you shipped in 100 (desktop) and 101 > (Android). > > On Monday, April 11, 2022 at 10:50:22 AM UTC-7 Joe Medley wrote: > >> Just saw where you answered t

[blink-dev] Intent to experiment: Deprecate and remove merchant identity in "canmakepayment"

Contact emailsrous...@chromium.org Specificationhttps://w3c.github.io/payment-handler/ Summary This is an early heads up that we intend to remove the merchant origin and arbitrary data from the "canmakepayment" service worker event of the Payment Handler API. These are the event fields to be rem