Electron Releases

Custom schemes registered with supportFetchAPI: true but without corsEnabled: true should return an opaque response to a cross-origin fetch(url, { mode: 'no-cors' }), the same as protocol.handle. The response was only tagged opaque on the string/buffer/stream path — registerFileProtocol and registerHttpProtocol delivered a readable (basic) response instead.

• Compute the opaque-response decision once in ElectronURLLoaderFactory::StartLoading and thread it into the file and http loaders.
• Tag the delivered response head kOpaque on the file and http paths via a small URLLoaderClient interposer, so asar, the plain file loader, and URLPipeLoader all match the buffer/stream path.
• Add protocol spec coverage for registerFileProtocol and registerHttpProtocol cross-origin no-cors fetches.

Notes: Fixed registerFileProtocol and registerHttpProtocol returning readable responses to cross-origin no-cors fetches; they now return opaque responses like protocol.handle.