scanner: Fix actions for stale regions appearing in new regions

To do so, we introduce an "image search token" - a weak pointer - which
is invalidated whenever the capture parameters (type, source, bounds -
excluding window) change during a session.

Using this, we get an image search token when
`CaptureModeController::PerformImageSearch()` is called, and pass it
down to `CaptureModeController::OnImageCapturedForSearch()`,
`CaptureModeController::OnTextDetectionComplete()` and
`CaptureModeController::OnScannerActionsFetched()`. If at any point the
image search token becomes invalidated, either the region changed or the
session shut down, so we abort.

This mitigates the issues coming from running the latter two
aforementioned methods on stale regions - specifically, adding multiple
"copy text" / "smart actions" buttons, and adding multiple Scanner
action buttons respectively. The manual checks for stale regions and
sessions are now a weak pointer check, and handles the case when a new
region has the same bounds as an old region.

Fixed: b:377602345, b:377570476, b:376168016
Change-Id: I6a6a2100a095ee800d450825a2d333925c7f4b5d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5999032
Auto-Submit: Michael Cui <mlcui@google.com>
Reviewed-by: Ahmed Fakhry <afakhry@chromium.org>
Commit-Queue: Michael Cui <mlcui@google.com>
Cr-Commit-Position: refs/heads/main@{#1380712}
8 files changed
tree: ace4038ba9d6eb9bd3dead32a985f4e6629a19f1
  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.