[M103][ios][ConfirmationAlertViewController] Add option to enclose image in view with shadow and badge

Previous uses of ConfirmationAlertViewController use an image
that already has a shadow baked into the image.

In FirstFollowViewController, we want to be able to set a
favicon image inside a frame view that has a shadow. These
favicons will not already have a shadow. Furthermore, we
want a green checkmark badge on the upper right corner.

New screenshots:
https://screenshot.googleplex.com/3pVdiNyHhwW4tzv.png
https://screenshot.googleplex.com/4QzpmWf3uRfEXZ9.png
https://screenshot.googleplex.com/4hgqHKo4te2UWko.png
https://screenshot.googleplex.com/9w5DkS82yNuWSsW.png
https://screenshot.googleplex.com/tjSscgwCB24NAjh.png
https://screenshot.googleplex.com/BzgXFprpyFpzZGu.png

This CL has not affected existing uses of
ConfirmationAlertViewController.

Existing uses of ConfirmationAlertViewController screenshots:
https://screenshot.googleplex.com/6PU9B6LkgFqKfQh.png
https://screenshot.googleplex.com/3CD9LkaiqY3uC67.png
https://screenshot.googleplex.com/5bj8TwAFVHgyiH8.png
https://screenshot.googleplex.com/3bZg6Lu6gF9QZ9o.png

(cherry picked from commit ba21cfb514060953f44c61885f2c4022aabfbed3)

Bug: 1327057
Change-Id: I82dc1556bc49d6fc411109f07ee2b01b32b0545c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3649311
Commit-Queue: edchin <edchin@google.com>
Reviewed-by: Sergio Collazos <sczs@chromium.org>
Cr-Original-Commit-Position: refs/heads/main@{#1005278}
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3656109
Cr-Commit-Position: refs/branch-heads/5060@{#144}
Cr-Branched-From: b83393d0f4038aeaf67f970a024d8101df7348d1-refs/heads/main@{#1002911}
4 files changed
tree: ef06c142ad17ee679a52e14fd3933115a44c551c
  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/
  22. fuchsia_webengine/
  23. gin/
  24. google_apis/
  25. google_update/
  26. gpu/
  27. headless/
  28. infra/
  29. ios/
  30. ipc/
  31. media/
  32. mojo/
  33. native_client_sdk/
  34. net/
  35. pdf/
  36. ppapi/
  37. printing/
  38. remoting/
  39. rlz/
  40. sandbox/
  41. services/
  42. skia/
  43. sql/
  44. storage/
  45. styleguide/
  46. testing/
  47. third_party/
  48. tools/
  49. ui/
  50. url/
  51. weblayer/
  52. .clang-format
  53. .clang-tidy
  54. .eslintrc.js
  55. .git-blame-ignore-revs
  56. .gitattributes
  57. .gitignore
  58. .gn
  59. .mailmap
  60. .rustfmt.toml
  61. .vpython
  62. .vpython3
  63. .yapfignore
  64. AUTHORS
  65. BUILD.gn
  66. CODE_OF_CONDUCT.md
  67. codereview.settings
  68. DEPS
  69. DIR_METADATA
  70. ENG_REVIEW_OWNERS
  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.