externalfile: scheme doesn't behave like file:
Reported by
jleedev@gmail.com,
Mar 3 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS armv7l 10176.72.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36 Platform: 10176.72.0 (Official Build) stable-channel daisy Steps to reproduce the problem: 1. Open a zip file in the file manager, or an sftp mount using the secure shell app. 2. Open an HTML file inside in the browser What is the expected behavior? I would expect that the document is treated the same as being from a file URL: Images, stylesheets, and classic scripts should be able to work. What went wrong? Documents loaded from the externalfile schema don't have access to any other resources from the same mount. This manifests as various errors and behaviors, but it all boils down to: I would expect this to be the same as a file URL, and it is not. Attempts to use fetch or module scripts fail (as expected) but with a slightly odd error: - "Invalid relative url or base scheme isn't hierarchical." - "Uncaught (in promise) TypeError: Failed to execute 'fetch' on 'Window': Failed to parse URL from ./ TypeError: Failed to execute 'fetch' on 'Window': Failed to parse URL from ./" (But this gives a clue as to why other resources don't load.) Links to images, stylesheets, and classic scripts show nothing at all in the network tab: Only the document ever appears. "View source" and then clicking a link opens a new tab at about:blank. Removing the file from the URL in an attempt to get a directory listing gives ERR_FAILED. Did this work before? N/A Chrome version: 64.0.3282.167 Channel: stable OS Version: 10176.72.0 Flash Version:
,
Mar 9 2018
,
Mar 12 2018
I'm not sure what expected behaviour should be, but I can reproduce with this file.
,
Mar 15 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by caseq@chromium.org
, Mar 5 2018