Revert spec to REC state #1021
Merged
Revert spec to REC state #1021
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcoscaceres
requested review from
ianbjacobs,
stephenmcgruer and
rsolomakhin
as code owners
This addresses this issue in SPC - https://w3c.github.io/secure-payment-confirmation/#issue-e92619e9 The behavior spec'd in SPC appears to already be followed in general Payment Request implementations already, based on testing in both Safari and Chrome, so it seems safe to just spec it here instead.
7 tasks
marcoscaceres
commented
Mar 18, 2024
marcoscaceres
commented
Mar 18, 2024
marcoscaceres
commented
Mar 18, 2024
ianbjacobs
approved these changes
Apr 22, 2024
rsolomakhin
reviewed
May 13, 2024
|
For process reasons we want to create a "CR Snapshot" that is the Recommendation unchanged, except for the status. Then we will immediately (as in the same day probably) publish a "CR Draft" that will include (1) all the changes since the Rec including removal of the user activation requirement and (2) the address stuff restored, except using contact picker API instead of defining a dictionary in PR API. I hope that sounds ok! |
This plan SGTM! |
rsolomakhin
approved these changes
May 13, 2024
stephenmcgruer
added a commit
that referenced
this pull request
Aug 21, 2024
As per the plan outlined in #1021#issuecomment-2107832273, we have now created the CR Snapshot and published a new CR Draft (https://www.w3.org/TR/payment-request/) that includes restoring the address changes. The only remaining work for that plan is to restore the previous changes that had been made since REC. Changes included: - [Spec] Relax user activation requirement for show() #1009 Additional edits on tops of above changes: - Add note linking to issue #1022 for discussion of user activation relaxing conditions Fixes #1025
stephenmcgruer
added a commit
that referenced
this pull request
Aug 21, 2024
As per the plan outlined in #1021#issuecomment-2107832273, we have now created the CR Snapshot and published a new CR Draft (https://www.w3.org/TR/payment-request/) that includes restoring the address changes. The only remaining work for that plan is to restore the previous changes that had been made since REC. Changes included: - [Spec] Relax user activation requirement for show() #1009 Additional edits on tops of above changes: - Add note linking to issue #1022 for discussion of user activation relaxing conditions Fixes #1025
ianbjacobs
pushed a commit
that referenced
this pull request
Sep 9, 2024
As per the plan outlined in #1021#issuecomment-2107832273, we have now created the CR Snapshot and published a new CR Draft (https://www.w3.org/TR/payment-request/) that includes restoring the address changes. The only remaining work for that plan is to restore the previous changes that had been made since REC. Changes included: - [Spec] Relax user activation requirement for show() #1009 Additional edits on tops of above changes: - Add note linking to issue #1022 for discussion of user activation relaxing conditions Fixes #1025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR gets us back to where we were when we went to REC. It cherry-picks all the editorial and xref fixes.
Additionally:
Preview | Diff