forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[PaymentRequest] Enable requiring user-activation for show()
This change makes the minimal changes needed to require user activation for show(). There will need to be follow-through clean-up work to remove code that was conditional on user-activation being present previously. Changes made: - Flip blink feature PaymentRequestRequiresUserActivation to 'stable'. - Change some web test expectations. - Add a few comments for follow-up cleanup. Intent to Deprecate and Remove thread: https://groups.google.com/u/1/a/chromium.org/g/blink-dev/c/xCW746n6XJI Bug: 825270 Change-Id: I89e6f68d74aae53619e08898d84ae8189ceb60f0 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3351294 Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Reviewed-by: Nick Burris <nburris@chromium.org> Reviewed-by: Mike West <mkwst@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/main@{#990992}
- Loading branch information
1 parent
b0d5444
commit a50420b
Showing
6 changed files
with
18 additions
and
11 deletions.
There are no files selected for viewing
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -1792,6 +1792,7 @@ | |
}, | ||
{ | ||
name: "PaymentRequestRequiresUserActivation", | ||
status: "stable", | ||
}, | ||
{ | ||
name: "PaymentRetry", | ||
|
4 changes: 2 additions & 2 deletions
4
...ink/web_tests/external/wpt/payment-request/payment-request-show-method.https-expected.txt
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
2 changes: 1 addition & 1 deletion
2
...y/blink/web_tests/external/wpt/payment-request/show-consume-activation.https-expected.txt
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
This is a testharness.js-based test. | ||
FAIL Calling share consumes user activation promise_rejects_dom: function "function() { throw e }" threw object "UnknownError: Renderer process could not establish or lost IPC connection to the PaymentRequest service in the browser process." that is not a DOMException SecurityError: property "code" is equal to 0, expected 18 | ||
FAIL Calling share consumes user activation promise_rejects_dom: function "function() { throw e }" threw object "InvalidStateError: Failed to execute 'show' on 'PaymentRequest': Already called show() once" that is not a DOMException AbortError: property "code" is equal to 11, expected 20 | ||
Harness: the test ran to completion. | ||
|
10 changes: 6 additions & 4 deletions
10
third_party/blink/web_tests/payments/payment-request-interface-expected.txt
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
10 changes: 6 additions & 4 deletions
10
...link/web_tests/virtual/basic-card-enabled/payments/payment-request-interface-expected.txt
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