Closed nunojpg closed 6 years ago
This question is best discussed on either the Secure Contexts specification or the Chromium issue tracker. I do not believe that individual specifications should deviate from established standards and behaviors in this space.
file:// is a Potentially Trustworthy origin, but it's currently being disallowed by Chromium/Chrome.
Will this be not specified further and up to Browser implementers? Do you think this is the right choice from Chrome?