Revert "Close Message Center Bubble asynchronously in destructor."

This reverts commit 56118287fa30280c1b841c45252fcef385b24d7d.

Reason for revert: Discovered there is one remaining crash case.

Original change's description:
> Close Message Center Bubble asynchronously in destructor.
>
> The Message Center and Quick Settings UI are peers owned by the Unified
> System Tray. Previously, when all notifications in the Message Center
> were removed, the Message Center would be in an unusual state - it would
> be hidden, but still active and focused. When the Esc accelerator is
> processed by the focus manager of the Unified System Tray, it would free
> the Message Center Bubble and close the widget synchronously from the
> destructor, causing NativeWidgetAura to fail when the Window properties
> are accessed after it has been freed from the heap.
>
> This fix changes the Message Center Bubble destructor to asynchronously
> close its widget. This retains the Widget after the
> NativeWidgetAura::Hide() call in NativeWidgetAura::Close(), preventing
> the window_ pointer from becoming invalid. The remaining logic for
> next/previous focusable already handles this state correctly -it won't
> focus the Message Center with Tab or Shift+Tab.
>
> Bug: 1251351
> Change-Id: I924c222c4bbfe08ea7a3e620531cee92d70596b3
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3207232
> Commit-Queue: Owen Wiggins <owx@chromium.org>
> Reviewed-by: Ahmed Mehfooz <amehfooz@chromium.org>
> Reviewed-by: Alex Newcomer <newcomer@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#934031}

Bug: 1251351
Change-Id: I319c15848f5f3c0cae74bf90b2738516111c2717
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3238033
Commit-Queue: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: Owen Wiggins <owx@chromium.org>
Reviewed-by: Ahmed Mehfooz <amehfooz@chromium.org>
Cr-Commit-Position: refs/heads/main@{#934106}
6 files changed
tree: 5498f4410441641ef5abd3c35ec0a7c4f77175cd
  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. codelabs/
  14. components/
  15. content/
  16. courgette/
  17. crypto/
  18. dbus/
  19. device/
  20. docs/
  21. extensions/
  22. fuchsia/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. jingle/
  32. media/
  33. mojo/
  34. native_client_sdk/
  35. net/
  36. pdf/
  37. ppapi/
  38. printing/
  39. remoting/
  40. rlz/
  41. sandbox/
  42. services/
  43. skia/
  44. sql/
  45. storage/
  46. styleguide/
  47. testing/
  48. third_party/
  49. tools/
  50. ui/
  51. url/
  52. weblayer/
  53. .clang-format
  54. .clang-tidy
  55. .eslintrc.js
  56. .git-blame-ignore-revs
  57. .gitattributes
  58. .gitignore
  59. .gn
  60. .mailmap
  61. .rustfmt.toml
  62. .vpython
  63. .vpython3
  64. .yapfignore
  65. AUTHORS
  66. BUILD.gn
  67. CODE_OF_CONDUCT.md
  68. codereview.settings
  69. DEPS
  70. DIR_METADATA
  71. ENG_REVIEW_OWNERS
  72. LICENSE
  73. LICENSE.chromium_os
  74. OWNERS
  75. PRESUBMIT.py
  76. PRESUBMIT_test.py
  77. PRESUBMIT_test_mocks.py
  78. README.md
  79. 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.