Use holding space image in file search

Makes launcher file results return an ImageSkia that lazily loads the file thumbnail image. This ensures that file result thumbnails are
loaded only when needed. Previously, thumbnails were requested for
every available file result, causing jank for queries that returned
large number of file results. To manage icon loading, reuses existing
`HoldingSpaceImage`, which solves the same problem in holding space UI.

File results are expected to display a placeholder, file type icon while
thumbnail is loading, which `HoldingSpaceImage` supports. Some
adjustments were needed for file results for image search - in this case
the UI shows a "pulsing" block animation in place of the icon. This was
achieved by search provider returning results with an null icon until
the thumbnail image was loaded. This does not work with the new
approach, as now FileResults return a non-null lazily loaded image.
This adds "is_placeholder" param to the result icon info, which can UI
uses to determine whether pulsing blocks need to be shown beneath
the result image view showing a placeholder image (which is set to an
empty image for file results for image search).

BUG=b/333648341, b/324083876

Change-Id: I995a1cfc6226830208b8ea7d4b49f2f194528a1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5503952
Reviewed-by: David Black <dmblack@google.com>
Commit-Queue: Toni Barzic <tbarzic@chromium.org>
Reviewed-by: Matthew Mourgos <mmourgos@chromium.org>
Reviewed-by: CJ Huang <chenjih@google.com>
Cr-Commit-Position: refs/heads/main@{#1297993}
18 files changed
tree: 86d7b2baaa0e1b2013c7a5fd77018d567df453bb
  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. .clangd
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitallowed
  57. .gitattributes
  58. .gitignore
  59. .gitmodules
  60. .gn
  61. .mailmap
  62. .rustfmt.toml
  63. .vpython3
  64. .yapfignore
  65. ATL_OWNERS
  66. AUTHORS
  67. BUILD.gn
  68. CODE_OF_CONDUCT.md
  69. codereview.settings
  70. CPPLINT.cfg
  71. DEPS
  72. DIR_METADATA
  73. LICENSE
  74. LICENSE.chromium_os
  75. OWNERS
  76. PRESUBMIT.py
  77. PRESUBMIT_test.py
  78. PRESUBMIT_test_mocks.py
  79. README.md
  80. 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.