Reland "Privacy Sandbox Settings: Pipe cr-dialog close to close function"

This is a reland of commit 31f14a5fe0d15ed734fa4e80d0739b491cfd1617

Original issue was with the test, production code OK. In some build
configs not all events related to close appeared to be queued sync.
CL adjusts logic to wait for final close report, and then element
logic update.

Original change's description:
> Privacy Sandbox Settings: Pipe cr-dialog close to close function
>
> Previously only button closes in the modal dialogs correctly updated
> the view state on the Privacy Sandbox settings page.
>
> This CL adjusts logic so that closes handled by the dialog element,
> such as via ESC, also correctly update the logic.
>
> Bug: 1324926
> Change-Id: Ic155464779814f5fd3b19448acda1c97da096e5f
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3644568
> Reviewed-by: Olesia Marukhno <olesiamarukhno@google.com>
> Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com>
> Cr-Commit-Position: refs/heads/main@{#1002654}

(cherry picked from commit 86eb5c7b57c2c87a4859b2bb5cb4071857f86784)

Bug: 1324926
Change-Id: Idda949e93aea430779950a14fcb9e520dd618329
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3645074
Commit-Queue: Theodore Olsauskas-Warren <sauski@google.com>
Reviewed-by: Olesia Marukhno <olesiamarukhno@google.com>
Cr-Original-Commit-Position: refs/heads/main@{#1003090}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3650612
Auto-Submit: Theodore Olsauskas-Warren <sauski@google.com>
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/5060@{#43}
Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
3 files changed
tree: 51e47e5db47f38d99ba8460a8337620b9c95bc60
  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/
  22. fuchsia_webengine/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  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. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  71. LICENSE
  72. LICENSE.chromium_os
  73. OWNERS
  74. PRESUBMIT.py
  75. PRESUBMIT_test.py
  76. PRESUBMIT_test_mocks.py
  77. README.md
  78. 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.