Reland "[PermissionOptions] Return PermissionResult in callback for requests"

This is a reland of commit 16f277ba00702c1ce679ccf94291ce51f1a7ab6a

The build failure was because the CastPermissionManager interface was not updated to the new PermissionControllerDelegate interface.

Original change's description:
> [PermissionOptions] Return PermissionResult in callback for requests
>
> This CL changes the callback type for permission requests to take a PermissionResult instead of a PermissionStatus. PermissionResults contain the PermissionStatus and can optionally contain the stored PermissionSetting, which is something that will need to be accessed by permissions with options, if they want to support permission downgrades (e.g. to detect that only coarse location was granted for a precise location request).
>
> To create a PermissionResult we use the PermissionStatus and set the PermissionStatusSource to UNSPECIFIED. Since the retrieved_permission_data member is an optional, we don't need to set it across the codebase. By default the permission context sets this member when permissions are set, which executes the permission request callback with this information (see PermissionContextBase::NotifyPermissionSet).
>
> Bug: 436773343
> Change-Id: Iaf4dfa2f1532db17a069eb6db032350f2a0d2019
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6818254
> Reviewed-by: Peter Conn <peconn@chromium.org>
> Reviewed-by: Ravjit Uppal <ravjit@chromium.org>
> Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
> Reviewed-by: Nico Weber <thakis@chromium.org>
> Reviewed-by: David Dorwin <ddorwin@chromium.org>
> Commit-Queue: Florian Jacky <fjacky@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1501523}

Bug: 436773343
Change-Id: I15f96cd7d1fc44ad7df0b375f125c54f025bab16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6851838
Reviewed-by: David Dorwin <ddorwin@chromium.org>
Commit-Queue: Florian Jacky <fjacky@chromium.org>
Reviewed-by: Ravjit Uppal <ravjit@chromium.org>
Reviewed-by: Nico Weber <thakis@chromium.org>
Reviewed-by: Yuchen Liu <yucliu@chromium.org>
Owners-Override: Nico Weber <thakis@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1503130}
99 files changed
tree: fe47d0e6b9850d065d61f0025b01f141dc017848
  1. .gemini/
  2. .github/
  3. agents/
  4. android_webview/
  5. apps/
  6. ash/
  7. base/
  8. build/
  9. build_overrides/
  10. buildtools/
  11. cc/
  12. chrome/
  13. chromecast/
  14. chromeos/
  15. codelabs/
  16. components/
  17. content/
  18. crypto/
  19. dbus/
  20. device/
  21. docs/
  22. extensions/
  23. fuchsia_web/
  24. gin/
  25. google_apis/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. net/
  34. pdf/
  35. printing/
  36. remoting/
  37. rlz/
  38. sandbox/
  39. services/
  40. skia/
  41. sql/
  42. storage/
  43. styleguide/
  44. testing/
  45. third_party/
  46. tools/
  47. ui/
  48. url/
  49. webkit/
  50. .clang-format
  51. .clang-tidy
  52. .clangd
  53. .cursorignore
  54. .geminiignore
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. CRYPTO_OWNERS
  72. DEPS
  73. DIR_METADATA
  74. LICENSE
  75. LICENSE.chromium_os
  76. OWNERS
  77. PRESUBMIT.py
  78. PRESUBMIT_test.py
  79. PRESUBMIT_test_mocks.py
  80. README.md
  81. SECURITY_OWNERS
  82. 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.