UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.102 Safari/537.36

Steps to reproduce the problem:
Steps to reproduce the problem:
1. Load a page that installs a service worker (maybe only specific sites?)
2. Simple reload will trigger the offline page from cache (or a connection error page)

What is the expected behavior?
What is the expected behavior?
1. Load a page that installs a service worker
2. Simple reload will load the same page from cache

What went wrong?
The Fetch API is successfully loading other resources, but fails (without additional context to the error message- only "Failed to fetch") when attempting to load the home page. When reloading, it attempts to load the home page via Fetch API and when it fails, it delivers the cached offline page (if available) or the browser's network connection error page.

Did this work before? Yes Chromium 66

Does this work in other browsers? Yes

Chrome version: 70.0.3538.102  Channel: stable
OS Version: OS X 10.14.1
Flash Version: 

After discussing this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=874173 with the extension developer he mentioned that it may not actually be caused by the extension. I wanted to check a few more production releases of Chrome and the problem I'm running into is still happening regardless of version (currently 70).

https://github.com/uBlockOrigin/uBlock-issues/issues/173

It only happens when that extension is installed/active, but the developer mentioned that it is related to *this* Chromium issue here:
https://bugs.chromium.org/p/chromium/issues/detail?id=834734

I'll admit that I'm a little beyond my knowledge of the inner workings of Chrome, so I'm afraid I can't add much more detail than the Github Issue transcript I provided, but I'm happy to provide any additional information needed to help troubleshoot this. The screenshots from the initial report here are still occurring for me (I've kept my notes in my own Github repo here: https://github.com/chrisblakley/Nebula/issues/1709).

To reiterate from the first issue, the test case I attached is just two basic Fetch API calls with 2 different pages. This is happening on my website: https://gearside.com/nebula/ and the test case I attached is a snippet I have inside of my service worker file. The console and Network tab in DevTools will show the "A" group as successful, but the B group will fail.

I'm sorry this is so confusing, but I've reached the limit of my abilities to troubleshoot this so I'm not entirely sure where the actual problem is, but it seems to have something to do with the initiator in Chrome and how it works with Service Workers (which is causing conflicts with extensions)...
 

Deleted: sw-fetch-api-test.js 655 bytes

sw-fetch-api-test.js 655 bytes View Download

Deleted: chrome-66-success.png 105 KB

	chrome-66-success.png 105 KB View Download

Deleted: chrome-error-console.png 72.6 KB

	chrome-error-console.png 72.6 KB View Download

Deleted: chrome-error-network.png 85.3 KB

	chrome-error-network.png 85.3 KB View Download