commit | 052519c85371d865059de7aa3e155da201942d8d | [log] [tgz] |
---|---|---|
author | Alex Chen <alexwchen@chromium.org> | Tue Jan 14 17:00:57 2025 |
committer | Chromium LUCI CQ <chromium-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jan 14 17:00:57 2025 |
tree | 5d245e6408ec0501b25af390eafd02c3a9213255 | |
parent | 058b0781f13c79d4b21c7def271a2b5511ce36f2 [diff] |
[omnibox][spark] Use policy set icon for aggregator keyword matches Currently, the icon URL for a search aggregator is not persisted. As a result, whenever a user uses a search aggregator and navigates to the destination URL, the icon URL of the favicon is updated automatically to the destination page's favicon. Since the icon URL for a search aggregator should only be set by policy, this change updates the TemplateURLService to exclude search aggregator TemplateURLs from typical favicon updating. As a result, keyword matches will render the policy set icon for aggregator keywords. If no icon URL is set, the default globe icon will be shown. Note: Currently, only icons hosted on a page that has been navigated to will show in the keyword match. Otherwise, the default globe icon is shown. A later CL will handle fetching the favicon without navigation. Screenshot of no icon set by policy/not navigated to icon URL: https://screenshot.googleplex.com/3H75GT6yopxp2yt Screenshot of icon set/navigated to: https://screenshot.googleplex.com/ARQ4R5iZrZX47Xm Bug: b:380509200 Change-Id: Ia65207154a2fdc73b2a9fc3c4418fc7d504f973c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6142954 Commit-Queue: Alex Chen <alexwchen@chromium.org> Reviewed-by: Fabio Tirelo <ftirelo@chromium.org> Reviewed-by: Moe Ahmadi <mahmadi@chromium.org> Cr-Commit-Position: refs/heads/main@{#1406135}
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.