Google Git
Sign in
chromium / chromium / src.git / 8fcb919e3946cce100e127ee13cb388b2d77c622
commit8fcb919e3946cce100e127ee13cb388b2d77c622[log] [tgz]
authorLiquan (Max) Gu <[email protected]>Wed May 20 16:22:18 2020
committerCommit Bot <[email protected]>Wed May 20 16:22:18 2020
tree05884c79966be63b0b27709199f914e27d27b39b
parenta5cc331299d5208e606de95085f0575de4915567 [diff]
[PlayBilling] AboutFlag permits AppStoreBilling TWA from any source

Context:
App store billing (knowned as Play Billing, for Google Play Store) is
the context where a TWA issues a PaymentRequest to request a transaction
with the app-store payment method. This CL imposes an restriction on
the TWA's source of installation and add an about flag to loosen the
restriction to facilitate local development & debugging.

Before:
The TWA can be installed from any source to be able to request the
app-store method.

After:
* By default, in order to request payments with an app-store payment
method, the TWA must be installed from the same app store.
* When users turn on the added about flag, they are allowed to use
an TWA from any source for the app-store billing purpose.

Change:
* Add an about flag: enable-debug-for-store-billing
* Add a restriction on the source of installation based on the flag's
state.

Bug: 1073936

Change-Id: I2213d979fcfc29085100ea7f71e4af508f376fb5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2199729
Reviewed-by: Yaron Friedman <[email protected]>
Reviewed-by: Rouslan Solomakhin <[email protected]>
Reviewed-by: Sahel Sharify <[email protected]>
Reviewed-by: Elly Fong-Jones <[email protected]>
Commit-Queue: Liquan (Max) Gu <[email protected]>
Cr-Commit-Position: refs/heads/master@{#770621}
15 files changed
tree: 05884c79966be63b0b27709199f914e27d27b39b
  1. android_webview/
  2. apps/
  3. ash/
  4. base/
  5. build/
  6. build_overrides/
  7. buildtools/
  8. cc/
  9. chrome/
  10. chromecast/
  11. chromeos/
  12. cloud_print/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. jingle/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .vpython
  60. .vpython3
  61. .yapfignore
  62. AUTHORS
  63. BUILD.gn
  64. CODE_OF_CONDUCT.md
  65. codereview.settings
  66. DEPS
  67. ENG_REVIEW_OWNERS
  68. LICENSE
  69. LICENSE.chromium_os
  70. OWNERS
  71. PRESUBMIT.py
  72. PRESUBMIT_test.py
  73. PRESUBMIT_test_mocks.py
  74. README.md
  75. WATCHLISTS
README.md

Logo Chromium

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.

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.