Intent to Experiment: Payment handler minimal header UX

183 views
Skip to first unread message

Nick Burris

unread,
Feb 22, 2023, 3:42:23 PM2/22/23
to blink-dev, Stephen McGruer

Contact emails

nbu...@chromium.orgsmcg...@chromium.org

Explainer

https://crbug.com/1385136 - see comment 14 for screenshot

Specification

Not applicable

Design docs


Summary

This is a refresh of the browser UI associated with the Payment Handler API. Although there are no changes to the API surface with this feature, we'd like to run an origin trial starting in M112 to give payment handler providers a chance to experiment with the new UI ahead of the launch.



Blink component

Blink>Payments

TAG review

Not applicable

TAG review status

Not applicable

Risks

Interoperability and Compatibility

None.


Gecko: N/A

WebKit: N/A

Web developers: No signals

Other signals:

WebView application risks

None.



Goals for experimentation

Allow developers using web-based payment handlers a chance to trial the new UI with their payment handler. We have a partner using payment handlers that has expressed desire to test this feature via an origin trial.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

No, Desktop platforms where Payment Request is implemented (Windows, Mac, Linux, Chrome OS).

Is this feature fully tested by web-platform-tests?

Not applicable.

Flag name

PaymentHandlerMinimalHeaderUX

Requires code in //chrome?

True

Estimated milestones

Origin Trial on desktop112


Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5079275637571584

This intent message was generated by Chrome Platform Status.

Yoav Weiss

unread,
Feb 23, 2023, 8:29:57 AM2/23/23
to Nick Burris, blink-dev, Stephen McGruer
That's an interesting application of an OT - basically you want to allow partner origins to experiment with the new UI in order to inform it? 

How many milestones do you want to run the trial on? 



Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5079275637571584

This intent message was generated by Chrome Platform Status.

--
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/CADvKJHMtKRBGSD-QvbUq1R2D8WUyJNELkGcWNN%3DT3E1OiL0Jjg%40mail.gmail.com.

Nick Burris

unread,
Feb 23, 2023, 11:21:35 AM2/23/23
to blink-dev, Yoav Weiss, blink-dev, Stephen McGruer, Nick Burris
On Thursday, February 23, 2023 at 9:29:57 AM UTC-4 Yoav Weiss wrote:
That's an interesting application of an OT - basically you want to allow partner origins to experiment with the new UI in order to inform it? 

Yes, an origin trial was specifically requested so they can get some real data using the new UI, and then iterate if necessary.
 

On Wed, Feb 22, 2023 at 9:42 PM Nick Burris <nbu...@chromium.org> wrote:
Contact emailsnbu...@chromium.orgsmcgruer@chromium.org

Explainerhttps://crbug.com/1385136 - see comment 14 for screenshot

SpecificationNot applicable


Design docs
Summary

This is a refresh of the browser UI associated with the Payment Handler API. Although there are no changes to the API surface with this feature, we'd like to run an origin trial starting in M112 to give payment handler providers a chance to experiment with the new UI ahead of the launch.



Blink componentBlink>Payments

TAG reviewNot applicable

TAG review statusNot applicable


Risks
Interoperability and Compatibility

None.


Gecko: N/A

WebKit: N/A

Web developers: No signals

Other signals:

WebView application risks

None.



Goals for experimentation

Allow developers using web-based payment handlers a chance to trial the new UI with their payment handler. We have a partner using payment handlers that has expressed desire to test this feature via an origin trial.

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?No, Desktop platforms where Payment Request is implemented (Windows, Mac, Linux, Chrome OS).


Is this feature fully tested by web-platform-tests?Not applicable.

Flag namePaymentHandlerMinimalHeaderUX

Requires code in //chrome?True

Estimated milestonesOrigin Trial on desktop112
How many milestones do you want to run the trial on? 

I think the default (6 milestones these days?) should be sufficient to give time for developers to run experiments and iterate.
 



Link to entry on the Chrome Platform Statushttps://chromestatus.com/feature/5079275637571584


This intent message was generated by Chrome Platform Status.
--
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+unsubscribe@chromium.org.

Yoav Weiss

unread,
Feb 24, 2023, 5:51:33 AM2/24/23
to Nick Burris, blink-dev, Stephen McGruer
LGTM to experiment M112-M117 (inclusive)

On Thu, Feb 23, 2023 at 5:21 PM Nick Burris <nbu...@chromium.org> wrote:


On Thursday, February 23, 2023 at 9:29:57 AM UTC-4 Yoav Weiss wrote:
That's an interesting application of an OT - basically you want to allow partner origins to experiment with the new UI in order to inform it? 

Yes, an origin trial was specifically requested so they can get some real data using the new UI, and then iterate if necessary.

Neat!!
Reply all
Reply to author
Forward
0 new messages