v2 works well, v3 works bad. How to make it works in v3?

[李白字一日]

v3:
url format = chrome-extension://aglmepmfibmokigfgakpbcimgkkkklia/_favicon/?pageUrl=https%3A%2F%2Fvideo.twimg.com&size=64
Screenshot from 2022-12-02 20-01-04

v2:
url format = chrome://favicon/size/32@1x/https://google.com/
Screenshot from 2022-12-02 19-07-30

but v2 is forbidden to be published.

[Jackie Han]

This problem is about how long the browser cache a favicon and how to handle it when there is no cache.

I asked this question at Comment 69, and got a response from an extension engineer at Comment 70:

I don't know how long they're cached nor do I know how to tell the browser to cache it longer. Would you be able to inspect the image with JS in some way to determine if it was a cache miss, and then implement your own fallback? This is a possible workaround.

I haven't tried to work around it yet, I suggest you report a bug or feature request.

--
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/b4428ed6-dd89-4553-ae93-6a2f89e0a629n%40chromium.org.

[李白|字一日]

Thanks.

My current work is to publish a version of my browser extension.

It was test with v2 and worked well.

But when I started to upload my package I found that v2 is no longer acceptable.

So I tried my best to update my code to be v3 compatible to find that v3 favicon api is not ready.

The urgent thing for me  is to enable me to publish a chrome extension package with v2.

Because issuing a bug and fixing it will take a very long time which is so expensive to me.

In fact,  I have issued a more detailed favicon api document request here: 

https://github.com/GoogleChrome/developer.chrome.com/issues/3286

I don't expect it will be fixed with a month.

For me the best solution would be that google accept v2 again before the favicon bug is fixed and a new favicon api is ready.

Jackie Han <han.g...@gmail.com> 于2022年12月4日周日 16:41写道：

[Jackie Han]

Unfortunately, this official blog (published September, 2021) said:

"January 17, 2022: New Manifest V2 extensions will no longer be accepted by the Chrome Web Store."

I don't think they will change it, especially since the new favicon API has landed in Chrome 104.

[李白|字一日]

You're right.

Technological giant companies are getting more and more dictatorial.

So I have to postpone my package development until the bug is fixed.

Jackie Han <han.g...@gmail.com> 于2022年12月4日周日 18:05写道：

[Robbi]

I'll tell you a secret @cali, but don't tell anyone, please!
Need to understand that little managers have goals to accomplish.
If those manager complete their goals then the great managers will make rain big money;
If, on the other hand, they do not respect the agreed deadlines, there will be ear-pulls (at the very least).
Therefore they will unlikely move deadlines forward. (in their language it would mean to have failed)
Going back to practical things, if your extension hasn't been published yet you can wait a few more months
or you can publish on Firefox Store which supports V2 and has not drawn up peremptory deadlines regarding migrations.
The matter is different for the already published V2 extensions that risk oblivion after the deadline.
"They are flying the aeroplane while they are still building it"
hmm, this sentence reminds me of something...

[李白|字一日]

Thanks. I will try to publish a firefox version first.

Robbi <rob...@gmail.com> 于2022年12月4日周日 21:22写道：

[Robbi]

You also save $5

Many successful extensions have focused their development on FF (for example this one)

[李白|字一日]

Just tried Firefox extension, and found that it doesn't support favicon api by now:)

Robbi <rob...@gmail.com> 于2022年12月5日周一 00:12写道：

[Robbi]

Firefox for the moment recommends publishing MV2 even if he already has an MV2.5 ready in his drawer.

If you want to test this way (only locally on your PC) you need to activate a flag on your browser (which I don't remember at the moment).

My advice is to proceed with MV2 in FF. It costs nothing and the experience can only benefit you :-)

With MV2, to get favicons you can use these urls: http://www.google.com/s2/favicons?domain_url=<host_name>

or https://t2.gstatic.com/faviconV2?client=SOCIAL&type=FAVICON&fallback_opts=TYPE,SIZE,URL&url=<host_name>&size=64

You can also create your own database of favIconUrls through the "tabs" permission and then use these urls first or as a falback of the above addresses