CR Snapshot and CR Draft Update Request for Payment Request API - payment-request
Closed this issue · 2 comments
Hello all,
Payment Request API was published as a Recommendation on 8 September 2022 . As part of that journey the Working Group removed some features related to addresses (shipping and billing) in response to feedback received during privacy and internationalization reviews. However, both Chromium and Webkit browsers had already shipped with support for the address features and, several years later, they continue to support those features. The browser implementers have requested that we re-align the specification with implementations and endeavor to resolve any previously raised issues.
For that reason, the Web Payments WG has reached a decision to request to republish Payment Request twice in quick succession:
- As a Candidate Recommendation snapshot with no changes from the Recommendation
- As a Candidate Recommendation Draft, restoring the features related to addresses.
That would achieve our goal of having a draft document on the TR page with features currently shipping in browsers, and we would then work to address the issues that were previously raised before advancing to Proposed Recommendation.
Document URLs
Link to group's decision to request transition
Link to previous Candidate Recommendation transition or update request
Substantive changes
The diff between CR Snapshot and CR Draft amounts to:
- Re-introduce addresses. Some of the material has been moved to another specification --Contact Picker API-- because standardized addresses are useful on the Web beyond payments. The updated Payment Request API retains much of the original text related to addresses, but also includes some references to Contact Picker API.
- Changes related to user activation
- Editorial fixes (e.g., due to changes in referenced specifications) and a bug fix (related to show() only being callable in a foreground tab).
Any changes in requirements?
None.
Wide Review of substantive changes
We believe the W3C Process allows us to publish these documents without first getting wide review of reintroduction of these features. We plan to get wide review before advancing to Proposed Recommendation.
Issues status
The Payment Request issues list.
Formal Objections
No new Formal Objections since publication of the Recommendation.
Any changes in implementation information?
As mentioned above, implementations are shipping support for the re-introduced address feature. Regarding removal of the user activation requirement, we do not yet have two implementations and are tracking that via issue 1025.
Deadline for further comments
1 October 2024
Any changes in patent disclosures?
None.
See Requirements for updating a Candidate Recommendation Snapshot for further information.
Approved.
Just in case you feel ambitious: the changelog in the CR snapshot contains the list of changes applied to CR Draft (eg it's listing the addition of the user activation requirement section even it's not part of the snapshot). Since the snapshot is meant to get replaced right away, that's ok.
Thank you @plehegar. I have sent a publication request to the Webmaster.