[PaymentRequest] Throw correct error when user activation missing The error thrown when user activation is missing was recently changed from NotAllowedError to SecurityError: https://github.com/w3c/payment-request/pull/961 This change has no effect on shipped Chrome yet as we currently don't throw at all for missing activation - the logic is hidden behind the capability delegation flag. Tested via unittest and via visiting https://wpt.live/payment-request/show-consume-activation.https.html with --enable-features=CapabilityDelegationPaymentRequest set. Bug: 1239453 Change-Id: I14f3874397468ca5da617afa930ffbbe254f1607 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3092912 Reviewed-by: Mustaq Ahmed <mustaq@chromium.org> Reviewed-by: Scott Violet <sky@chromium.org> Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org> Commit-Queue: Stephen McGruer <smcgruer@chromium.org> Cr-Commit-Position: refs/heads/master@{#911813}
Chromium is an open-source browser project that aims to build a safer, faster, and more stable way for all users to experience the web.
The project's web site is https://www.chromium.org.
To check out the source code locally, don't use git clone! Instead, follow the instructions on how to get the code.
Documentation in the source is rooted in docs/README.md.
Learn how to Get Around the Chromium Source Code Directory Structure .
For historical reasons, there are some small top level directories. Now the guidance is that new top level directories are for product (e.g. Chrome, Android WebView, Ash). Even if these products have multiple executables, the code should be in subdirectories of the product.
If you found a bug, please file it at https://crbug.com/new.