Google GitGoogle Git
Sign in
chromium/chromium/src/194f8902a41019d4e4eac736af62da2d075ae798
commit
194f8902a41019d4e4eac736af62da2d075ae798
[log]
author
Neil Coronado <nemco@google.com>
Sat Sep 19 00:22:35 2026
committer
Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com>
Sat Sep 19 00:22:35 2026
tree
895fe33bdb1ca8449924c1fc4a7b572e225cb603
parent
6bad8a0dd93d287b22dab640ed9d4288b4fffd5f [diff]
[M155] [TabStrip] Increase tab strip favicon resolution

Original change's description:
> [TabStrip] Increase tab strip favicon resolution
>
> Increase tab strip favicon resolution.
> -Update tab_favicon to account for the device scale factor when
>  requesting favicons on Android.
>
> Comparison: http://screenshot-v2/image/0uojvl30s526o.png
>
> Bug: 559781869
> Change-Id: I5bba0100d8611208c11857da3b5d09dadb628a5d
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8414815
> Reviewed-by: Calder Kitagawa <ckitagawa@chromium.org>
> Commit-Queue: Neil Coronado <nemco@google.com>
> Cr-Commit-Position: refs/heads/main@{#1699078}

(cherry picked from commit 8cddd4646f7e47f7e4f4483defe3c75f554986dd)

Bug: 563063533,559781869
Change-Id: I5bba0100d8611208c11857da3b5d09dadb628a5d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/8429144
Bot-Commit: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com>
Commit-Queue: rubber-stamper@appspot.gserviceaccount.com <rubber-stamper@appspot.gserviceaccount.com>
Auto-Submit: chrome-cherry-picker@chops-service-accounts.iam.gserviceaccount.com <chrome-cherry-picker@chops-service-accounts.iam.gserviceaccount.com>
Cr-Commit-Position: refs/branch-heads/8059@{#212}
Cr-Branched-From: 199ac2cd7ab289e11c2236bd2cede848781213da-refs/heads/main@{#1697595}
2 files changed
tree: 895fe33bdb1ca8449924c1fc4a7b572e225cb603
  1. .agents/
  2. .claude/
  3. .gemini/
  4. .github/
  5. agents/
  6. android_webview/
  7. apps/
  8. ash/
  9. base/
  10. build/
  11. build_overrides/
  12. buildtools/
  13. cc/
  14. chrome/
  15. chromecast/
  16. chromeos/
  17. codelabs/
  18. components/
  19. content/
  20. crypto/
  21. dbus/
  22. device/
  23. docs/
  24. extensions/
  25. fuchsia_web/
  26. gin/
  27. google_apis/
  28. gpu/
  29. headless/
  30. infra/
  31. ios/
  32. ipc/
  33. media/
  34. mojo/
  35. net/
  36. pdf/
  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. webkit/
  52. clank
  53. clusterfuzz-data
  54. internal
  55. ios_internal
  56. signing_keys
  57. v8
  58. .clang-format
  59. .clang-tidy
  60. .clangd
  61. .cursorignore
  62. .geminiignore
  63. .git-blame-ignore-revs
  64. .gitallowed
  65. .gitattributes
  66. .gitignore
  67. .gitmodules
  68. .gn
  69. .mailmap
  70. .rustfmt.toml
  71. .vpython3
  72. .yapfignore
  73. ATL_OWNERS
  74. AUTHORS
  75. BRANCH_FEATURE_OWNERS
  76. BRANCH_OWNERS
  77. BUILD.gn
  78. CODE_OF_CONDUCT.md
  79. codereview.settings
  80. CPPLINT.cfg
  81. CRYPTO_OWNERS
  82. DEPS
  83. DIR_METADATA
  84. LICENSE
  85. LICENSE.chromium_os
  86. OWNERS
  87. package.json
  88. PRESUBMIT.py
  89. PRESUBMIT_test.py
  90. PRESUBMIT_test_mocks.py
  91. README.md
  92. SECURITY_OWNERS
  93. vpython.toml
  94. vpython.toml.uv.lock
  95. 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.