Make FaviconService clients more consistent |
|||
Issue descriptionAs of today, FaviconService offers their clients (NTP, bookmark UI, sync, etc.) a very flexible API that has two important downsides: 1. It is hard to honor during actual favicon fetching on page load. 2. It can lead to inconsistent UIs. We'd like to gather what the actual requirements are for each client, and hopefully make them more explicit in the API.
,
Apr 18 2017
,
Dec 18 2017
This idea probably still makes sense but given its low priority and the project handover to Seattle, it's very unlikely that anything happens, hence closing it. |
|||
►
Sign in to add a comment |
|||
Comment 1 by mastiz@chromium.org
, Mar 9 2017