Yeah, that’s true. But since Firefox is throwing this error around (Corrupted Content) for any network level error that happens in a fetch inside a service worker my guess is that it’s a red herring for connectivity problems, aka the page wouldn’t load anyway but with a different error.
And until someone can give proper reproduction steps like I did above, it’s hard to come up with new hypothesis.