This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 973
Ship hard-coded search engine favicons #12689
Labels
Milestone
Comments
We'll need the favicon cache from #2697 to update them based on user activity. Until that's available, I'd prefer to ship hardcoded icons for these sites to avoid making non-user-initiated requests. |
related to #11108 |
shipping hardcoded icons is easy. i think we will probably do that first and have a follow up issue for cache invalidation |
@flamsmark unless i'm misunderstanding, let's use #2697 for the caching issue (which would also apply to bookmarks, etc.) and use this issue for hard-coding favicons in the browser search panel |
10 tasks
tildelowengrimm
changed the title
Ship cached search engine favicons
Ship hard-coded search engine favicons
Jan 18, 2018
Going to mark for 0.20.x since it is an easy privacy win and relatively low-risk code change |
This was referenced Jan 24, 2018
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Test plan
#12698
Original issue description
Per @liunkae's comment on #12632, we automatically try to fetch favicons for search engines shipped in about:preferences#search. We shouldn't make any non-user-initiated requests to those sites. I'd like to shipped cached favicons for those sites, and have the search UI only read out of the favicon cache. That way, we can always show icons shown in the search pane, they'll always be as current as our latest release. If a user regularly visits a site and that site updates their icon, the user will see a newer icon in the search pane based on the timing of their recent visits.
The text was updated successfully, but these errors were encountered: