Intent to Ship: Payment handler minimal header UX

[Rouslan Solomakhin]

Contact emails
nbu...@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-VMUV90L2bb2OqlrBVepW4A#heading=h.bat9awopsp53

Summary
This is a refresh of the browser UI associated with the Payment Handler API. There are no API changes. The origin trial is concluding and we'd like to ship this feature in M119. See R2E for more details.

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: No signals

WebView application risks

None

Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No

Debuggability
N/A because it is a UI-only change.

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

Is this feature fully tested by web-platform-tests?
No, because this is a UI-only change.

Flag name
PaymentHandlerMinimalHeaderUX

Finch feature name
None

Non-finch justification
None

Requires code in //chrome?
True

Estimated milestones
Shipping on desktop: 119

Anticipated spec changes

N/A, because there is no spec for a UI-only change.

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

Links to previous Intent discussions
Intent to Experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/NQ-WLvfmPs8/m/hDKJNnmOBgAJ

This intent message was generated by Chrome Platform Status.

[Mike Taylor]

LGTM1 (I'm not sure you need our approvals to ship this UX change, but you can have mine).

--
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/CAMMzaWEp6JQOKeYBjkhGa_w%3DQvDuEOPZu590FrDLj3%2Bg2eWQWQ%40mail.gmail.com.

[Daniel Bratell]

LGTM2 (Also not sure you need this approval, but you can have mine as well)

/Daniel

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/4c3078ba-ab44-4c54-96d9-5a9ba36a5523%40chromium.org.

[Stephen Mcgruer]

Thanks Mike! We were following through on the I2S process because we did an I2E for this feature as a way to let folks verify that the UX change wouldn't cause regressions.

I still think that is correct as follow-through, but we could probably have made it clearer than we hope this I2S will be a rubber stamp for API owners. (Or... maybe we should have just sent a PSA? Anyhow, we are here now).

[Rick Byers]

LGTM3 as not subject to blink process.  But thanks for the heads up!

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADY3MaebhFbQuF5SF4NbzXS0Gbc3vb3SCgmc%3DE9KKKQ7VGG1Uw%40mail.gmail.com.