MV3 User authored userscripts and favicon access

[Kyle Paulsen]

I'm maintaining a couple extensions. One of them is similar to tampermonkey and allows user written scripts to be injected (userscripts). I've heard that support for this is coming in MV3. Does anyone know when? Is there a main chromium ticket tracking this? There is very little time left to implement and test this if MV2 extensions are being removed Jan 1st 2023.

I also have a bookmark manager like extension that uses the "chrome://favicon/" permission (which is being removed in MV3). Is there support for this coming soon? When? Is there a main chromium ticket tracking this?

Thanks.

[Jackie Han]

New Favicon API has landed in Chrome 104 Stable. You can use it now.

Example:

https://groups.google.com/a/chromium.org/g/chromium-extensions/c/qS1rVpQVl8o/m/qmg1M13wBAAJ

https://groups.google.com/a/chromium.org/g/chromium-extensions/c/qS1rVpQVl8o/m/W710P0bxBAAJ

--
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.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/f5a7e940-fada-4b9a-a21b-bb79fb4153a1n%40chromium.org.

[Kyle Paulsen]

Thank you for the favicon info! Glad to see it working in MV3.

Now I hope we can get userscript support soon.

[Jackie Han]

One more note for the new favicon api: Permission favicon is a warning permission if you don't have other related permission (like browsing history permission).