chrome.favicons

1,256 views
Skip to first unread message

Marco Foit

unread,
Sep 17, 2020, 4:05:42 AM9/17/20
to Chromium Extensions
Hi there!

Is there any news about that new proposed favicons api (chrome.favicons)?
If so, does the new api cover large website icons (> 16*16 pixel)?

Favicons play an important part in my Favorites extension *).
Having a roadmap for possible api changes would be highly appreciated.

Thank you!

Cheers,
Marco


*)
https://chrome.google.com/webstore/detail/favorites-new-tab-page/kjkbcegjfanmgocnecnngfcmmojheiam

Simeon Vincent

unread,
Sep 23, 2020, 3:02:22 AM9/23/20
to Chromium Extensions
Hey Marco,

I don't have any updates on this API. It's still on our backlog, but for the moment we're focusing on trying to get an MVP of Manifest V3 into the stable channel. Besides larger access to larger icons, are there any other capabilities you're especially interested in?

Cheers,

Simeon - @dotproto
Developer Advocate for Chrome Extensions

Marco Foit

unread,
Sep 23, 2020, 4:15:59 AM9/23/20
to chromium-...@chromium.org
Hi Simeon!

Thank you very much for your response.

> Besides larger access to larger icons, are there any other capabilities you're especially interested in?

In general, a well-engineered unified promise-based browser API for
large website icons / favicons would be great.

With caching etc. and its own api permission (*or* an implicit
permission as part of a more 'general bookmarks api permission').

The situation right now is not good for many reasons.
To cite the draft of Manifest V3 (Nov 2018):

"[...] Currently, extensions can request chrome://favicon as host
permission, and this allows them to fetch a website’s favicon by
fetching chrome://favicon/https://example.com (for example.com`’s
favicon). This has caused us endless grief. [...]"

Cheers,
Marco









Am 23.09.20 um 09:02 schrieb Simeon Vincent:
> <https://chrome.google.com/webstore/detail/favorites-new-tab-page/kjkbcegjfanmgocnecnngfcmmojheiam>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Chromium Extensions" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to chromium-extens...@chromium.org
> <mailto:chromium-extens...@chromium.org>.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/66798563-2872-48ee-978e-ad6d9de41e1bo%40chromium.org
> <https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/66798563-2872-48ee-978e-ad6d9de41e1bo%40chromium.org?utm_medium=email&utm_source=footer>.

ilyaigpetrov

unread,
Oct 25, 2020, 12:16:45 AM10/25/20
to Chromium Extensions, Marco WA
> Besides larger access to larger icons, are there any other capabilities you're especially interested in?

Capability to set a custom icon for a website or modify original favicon to display some info above the icon (I guess it can be done via canvas html5 api).

ilyaigpetrov

unread,
Oct 25, 2020, 12:18:38 AM10/25/20
to Chromium Extensions, ilyaigpetrov, Marco WA
2) Capability to listen to favicon changes (if some site has notifications via icon then we may listen for its changes). Listening to icon changed not by site but by an extension also may be a good capabilty.

ilyaigpetrov

unread,
Oct 25, 2020, 12:36:50 AM10/25/20
to Chromium Extensions, Marco WA
Marco@, how did you learn about chrome.favicons API? I can't find much info about it.
And should we create a feature request at http://bugs.chromium.org?

Marco Foit

unread,
Oct 25, 2020, 4:34:31 AM10/25/20
to ilyaigpetrov, Chromium Extensions
A new favicon api was mentioned in the draft to Manifest v3.
But since then, I haven't heard anything about it.

https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3NzzhHzc-qnk4w4PX-0XMw8/edit#heading=h.wm0l12b5ayff

Cheers,
Marco


Am 25.10.20 um 05:35 schrieb ilyaigpetrov:
> example.com <http://example.com>`’s

Neal Fultz

unread,
Feb 13, 2021, 1:00:11 PM2/13/21
to Chromium Extensions, Marco WA, ilyaigpetrov
I'm trying to update my extension from MV2 => MV3, following the conversion guide I tried:

    "host_permissions": ["chrome://favicon/"],
    "content_security_policy": {
          "extension_pages": "default-src 'self' ; img-src chrome://favicon/"
    },

That has an "invalid scheme" error. 

Using the wildcard

    "host_permissions": ["*://favicon/"],

installs cleanly, but the favicon is blocked with this error message:

    Not allowed to load local resource: chrome://favicon/https://www.google.com/

"favicon" isn't recognized as a valid permission, either. It seems like MV3 just doesn't have favicons anymore. I guess I should just use direct linking for now?




wOxxOm

unread,
Feb 14, 2021, 9:55:57 AM2/14/21
to Chromium Extensions, Neal Fultz, Marco WA, ilyaigpetrov
It's not yet implemented. Click the star icon in https://crbug.com/104102 to be notified of progress. Don't expect it to happen soon.
Reply all
Reply to author
Forward
0 new messages