Rename 'type' field to 'operation'.

This CL is a step towards getting fetch API changes from the Private
State Token (PST, formerly known as TrustTokens) explainer. After
this CL fetch API will be as follows.

fetch('<issuer>/<issuance path>', {
  trustToken: {
    operation: 'token-request',
    issuer: <issuer>
  }
}).then(...)

Ultimately, we would like to be compatible with the explainer and have
the fetch API as follows.

fetch('<issuer>/<issuance path>', {
  privateToken: {
    type: 'private-state-token',
    version: 1,
    operation: 'token-request',
    issuer: <issuer>
  }
}).then(...)

This API creates room for supporting new type of tokens with backward
compatibility. It also supports having different versions of the PST coexist.

The edits in this CL stems from the the following two sources.

- In ./services/network/public/mojom/trust_tokens.mojom: Rename
  TrustTokenParams's 'type' field to 'operation'. Rename
  TrustTokenOperationResult's 'type' field to 'operation'.

- In ./thirdparty/blink/renderer/core/fetch/trust_token.idl: Rename
  'type' to 'operation'.

Bug: 1404729
Fixed: 1404730
Explainer: https://github.com/WICG/trust-token-api
Spec: https://wicg.github.io/trust-token-api/
Change-Id: I4742bd8e24c4437f35f6d2ccc08caf9dab7ae139
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4126918
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Aykut Bulut <aykutb@google.com>
Reviewed-by: Russ Hamilton <behamilton@google.com>
Reviewed-by: Steven Valdez <svaldez@chromium.org>
Reviewed-by: Avi Drissman <avi@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1094573}
48 files changed
tree: 44b70a842b74ac48544f4554ea4c9c63d6665388
  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. codelabs/
  13. components/
  14. content/
  15. courgette/
  16. crypto/
  17. dbus/
  18. device/
  19. docs/
  20. extensions/
  21. fuchsia_web/
  22. gin/
  23. google_apis/
  24. google_update/
  25. gpu/
  26. headless/
  27. infra/
  28. ios/
  29. ipc/
  30. media/
  31. mojo/
  32. native_client_sdk/
  33. net/
  34. pdf/
  35. ppapi/
  36. printing/
  37. remoting/
  38. rlz/
  39. sandbox/
  40. services/
  41. skia/
  42. sql/
  43. storage/
  44. styleguide/
  45. testing/
  46. third_party/
  47. tools/
  48. ui/
  49. url/
  50. weblayer/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gn
  58. .mailmap
  59. .rustfmt.toml
  60. .vpython3
  61. .yapfignore
  62. ATL_OWNERS
  63. AUTHORS
  64. BUILD.gn
  65. CODE_OF_CONDUCT.md
  66. codereview.settings
  67. DEPS
  68. DIR_METADATA
  69. LICENSE
  70. LICENSE.chromium_os
  71. OWNERS
  72. PRESUBMIT.py
  73. PRESUBMIT_test.py
  74. PRESUBMIT_test_mocks.py
  75. README.md
  76. 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.

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.