Howdy fellow extension makers, I'm an indie dev and recently started to share my monthly progress of the voyage. It's tough but fun at the same time.
I'm sharing my retro blog article, but wanted to put focus on a particular issue I encountered recently.
This is related to manifest v3 for Chrome. Long story short, service workers in the background break. Why? Well, that's the interesting part, it's not entirely clear but the culprit seems to be iFrames injected into a webpage. Silly right?
Well after a long weekend of attempting to identify the problem, I was able to come up with an example project that does these simple things.
chrome.commandsshortcut to inject an iFrame
updatelifecycle and service worker breaks 💥
Yeh, just these simple steps. Kind of annoying if you ask me.
Well, it's been 10 days since I've reported the bug, not much I can do really. I can't ship my extension with manifest v3 as it'll break for users the second I upgrade my users.
So what's next for me? I see no way other than to migrate to manifest v2. This means having to refactor my background script to support it, such a shame. All this time my goal with manifest v3 was to get ahead of the curve.
Here's the bug report for anyone interested: https://bugs.chromium.org/p/chromium/issues/detail?id=1242225#c1
My hope is to spread the word of this peculiar issue and be wary of using manifest v3, until it's been vetted by Google
PS: I really hope this is my fault and I can fix it, but after studying the scenario I just don't see how.