Chrome Version       : 60.0.3112.50 (Mac OS X)
Other browsers tested:
  Add OK or FAIL, along with the version, after other browsers where you
have tested this issue:
     Safari: - (not tested)
    Firefox: Kind of fails (see below for explanation)
         IE: - (not tested)

What steps will reproduce the problem?
(1) Clear Browser Cache (check that list of cached urls chrome://cache/ is empty)
(2) In the console create a new request that should irgnore the browser cache via execute `var req = new Request('https://service-worker-test.app.baqend.com/img/38.jpg', {cache: 'no-store'});`
(3) Fetch the request via `fetch(req)`
(4) Check back with chrome://cache/ and see that the response gets cached.

What is the expected result?
According to the specification of the fetch API (https://fetch.spec.whatwg.org/) the response to the above request should not be cached. 
From the specification: "'no-store' Fetch behaves as if there is no HTTP cache at all.".

What happens instead?
The response gets cached according to chrome://cache/.

Firefox Behaviour:
Firefox does not cache the response (according to about:cache) but also fails to cache any other response when using the fetch api from the console.