Revert "Add 'is ready to pay' restriction for Web Payment Handlers on Android" This reverts commit c1b17568a712e0a3f69c7f7b1c47608cf358b002. Reason for revert: Was causing CQ bot failures: https://ci.chromium.org/ui/p/chrome/builders/ci/chromium-internal-arm-builder Original change's description: > Add 'is ready to pay' restriction for Web Payment Handlers on Android > > This CL adds logic to check the state of the canMakePayment pref before > issuing the 'is ready to pay' query to service worker payment handlers > on Android. > > This CL also updates the `PaymentAppFactoryDelegate` interface by > removing the default implementation of `prefsCanMakePayment()`, forcing > all implementers to provide one. > > Bug: 427918761 > Change-Id: Id62b6afae9958d7bfa0e54680041b80b61d7f428 > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6936490 > Reviewed-by: Rouslan Solomakhin <rouslan@chromium.org> > Commit-Queue: Joshua Hood <jdh@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1516002} Bug: 427918761 No-Presubmit: true No-Tree-Checks: true No-Try: true Change-Id: If5ac8f23fe8b5bbdade07edfa149495d230d0cfa Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6955225 Commit-Queue: Kartar Singh <kartarsingh@google.com> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Owners-Override: Kartar Singh <kartarsingh@google.com> Cr-Commit-Position: refs/heads/main@{#1516017}
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.