MV3: chrome.action.setIcon makes a request everytime It's called

[Oluwatomi Alagbe]

Hello. 

I'm an engineer on the Malwarebytes browserguard team. 
We recently migrated our extension to MV3 and we noticed that everytime we make a call to the chrome.action.setIcon API we see a corresponding network request for the Icon in the Network tab of the developer tools. This is not the case in MV2. 

Is this a bug? Are there any performance consequences of this that we need to be worried about?

Best regards.

[woxxom]

If you change the icon a lot e.g. for each tab, consider caching imageData from Canvas/OffscreenCanvas yourself, because Chrome doesn't cache it and re-reads the icon file each time for each time for each specified icon size, both in MV2 and MV3.

[Oluwatomi Alagbe]

Thanks for the tip