You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Another issue arising from PR #273, in order to get the best possible performance, favicons are loaded directly from the Chrome favicon cache (chrome://favicon/). This is amazing for performance because there's no remote network requests slowing down page rendering.
The issue arises in that when you open a website for the first time and its favicon is not in the cache, it will never change from the default favicon, even after the chrome.tabs.onUpdated event. Apparently it can take a moment for the favicon to be added to the cache but its well after the tab update event has fired.
There are some existing Chrome bugs which could be related to this but we might still be able to implement a workaround using a combination of chrome://favicon/ and changeInfo.favIconUrl in the meantime.
Another issue arising from PR #273, in order to get the best possible performance, favicons are loaded directly from the Chrome favicon cache (
chrome://favicon/
). This is amazing for performance because there's no remote network requests slowing down page rendering.The issue arises in that when you open a website for the first time and its favicon is not in the cache, it will never change from the default favicon, even after the
chrome.tabs.onUpdated
event. Apparently it can take a moment for the favicon to be added to the cache but its well after the tab update event has fired.There are some existing Chrome bugs which could be related to this but we might still be able to implement a workaround using a combination of
chrome://favicon/
andchangeInfo.favIconUrl
in the meantime.Related:
The text was updated successfully, but these errors were encountered: