[mullet m2] Run callbacks when editor dialog is closed.

This CL is a scaffolding for later changes which make address
editor re-open AutofillPopup upon editor dismissal. This is only
possible to do once the source window receives the focus back.

When the user clicks one of the dialog's buttons, the corresponding
callback is invoked. Then the focus is returned back to the web
contents. The Autofill popup can only be opened in a focused web
contents, so we have to start opening the popup after the focus has
been transferred back to the previously focused form field. This can
be achieved by running the dialog callbacks when the dialog window is
being closed.

Instead of running the dialog callbacks when the dialog window is being
closed, another on_window_closed callback could've been introduced.
This would increase the total number of editor callbacks to 3. In
reality, editor needs only 1 callback, which accepts the user decision
and the modified autofill profile. This will be implemented in the
subsequent CL.

Bug: 1459990
Change-Id: I99e13483ff061d1442a5ed980295dbad2117a0df
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4847411
Reviewed-by: Vasilii Sukhanov <vasilii@chromium.org>
Commit-Queue: Timofey Chudakov <tchudakov@google.com>
Reviewed-by: Bruno Braga <brunobraga@google.com>
Cr-Commit-Position: refs/heads/main@{#1199518}
8 files changed
tree: 55ba2f73b5cf672d7842cbf15b27a054eaa51d97
  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. webkit/
  51. .clang-format
  52. .clang-tidy
  53. .eslintrc.js
  54. .git-blame-ignore-revs
  55. .gitattributes
  56. .gitignore
  57. .gitmodules
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython3
  62. .yapfignore
  63. ATL_OWNERS
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. LICENSE
  71. LICENSE.chromium_os
  72. OWNERS
  73. PRESUBMIT.py
  74. PRESUBMIT_test.py
  75. PRESUBMIT_test_mocks.py
  76. README.md
  77. 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.