Reland "[omnibox] Clear shortcuts with deleted/inactive keywords"

This is a reland of commit 56516be43412f3998e73e56694cbe2818a7fe9d6

Original change was reverted due to lifetime issue (UaF) for `template_url_service_observation_`. Patch calls `template_url_service_observation_.Reset()` to stop the ongoing observation before the `template_url_service_observation_` is destroyed.

Original change's description:
> [omnibox] Clear shortcuts with deleted/inactive keywords
>
> Currently, when a search engine is deleted/inactive, any shortcuts from
> the search engine will still show as shortcut suggestions. As a result,
> formatting of those suggestions are not formatted properly since the
> keyword of the suggestions does not exist in the TemplateURLService. For
> example, if a search was made in scoped mode, the unscoped result after
> engine deletion may show "keyword foo query".
>
> For inactive search engines, a user would not expect shortcuts to
> keywords while they're deactivated.
>
> This change adds an observer to the ShortcutsBackend to check for
> deleted/inactive keywords whenever the TemplateURLService is updated.
> This will ensure shortcut suggestions with keywords that have been deleted
> or inactive are removed.
>
> A future improvement could include suppressing corresponding history
> provider suggestions as well.
>
> Before: https://screenshot.googleplex.com/4GikJdoAz5MhVUn
> After: https://screenshot.googleplex.com/KZGWQjwYTTTk8qH
>
> Bug: 406761194
> Change-Id: I36bf0e3b18dd1ad60d3356db38e807be34fdbc3a
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6416724
> Commit-Queue: Alex Chen <alexwchen@chromium.org>
> Reviewed-by: manuk hovanesian <manukh@chromium.org>
> Cr-Commit-Position: refs/heads/main@{#1444371}

Include-Ci-Only-Tests: chromium.memory:Linux ASan LSan Tests (1)|browser_tests
Bug: 406761194
Change-Id: I379c91b00bc7a33972818d2305ea20090079b3fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6438704
Commit-Queue: Alex Chen <alexwchen@chromium.org>
Reviewed-by: manuk hovanesian <manukh@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1444850}
4 files changed
tree: 32068639455f315540f6c3175b42c1e72a9e1136
  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. crypto/
  16. dbus/
  17. device/
  18. docs/
  19. extensions/
  20. fuchsia_web/
  21. gin/
  22. google_apis/
  23. gpu/
  24. headless/
  25. infra/
  26. ios/
  27. ipc/
  28. media/
  29. mojo/
  30. native_client_sdk/
  31. net/
  32. pdf/
  33. ppapi/
  34. printing/
  35. remoting/
  36. rlz/
  37. sandbox/
  38. services/
  39. skia/
  40. sql/
  41. storage/
  42. styleguide/
  43. testing/
  44. third_party/
  45. tools/
  46. ui/
  47. url/
  48. webkit/
  49. .clang-format
  50. .clang-tidy
  51. .clangd
  52. .git-blame-ignore-revs
  53. .gitallowed
  54. .gitattributes
  55. .gitignore
  56. .gitmodules
  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. CPPLINT.cfg
  68. CRYPTO_OWNERS
  69. DEPS
  70. DIR_METADATA
  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.