The Fetch Specifications say that the default Fetch mode is 'no-cors' -
A request has an associated mode, which is "same-origin", "cors", "no-cors", "navigate", or "websocket". Unless stated otherwise, it is "no-cors".
But, I seem to be noticing this behavioral difference between mode: 'no-cors' and an unspecified mode. As demonstrated in this JSFiddle sample, explicitly defining mode as 'no-cors' makes the response inaccessible to the Javascript, while not specifying a mode makes the Response object available to the calling method.
Does explicitly specifying the fetch mode work differently from the default behavior that internally uses the same mode? What am I missing here?