How allowing many features of https:// protocol to a file:/// scheme would be an easy way to introduce security vulnerabilities into browsers?
Assume that someone is accessing his webpage locally using file:/// protocol and he/she is not using local server to access or view a webpage, then how allowing many features of https:// protocol to file:/// protocol as well can introduce security vulnerabilities into browsers?
How allowing many features of https:// protocol to a file:/// scheme would be an easy way to introduce security vulnerabilities into browsers?
Assume that someone is accessing his webpage locally using file:/// protocol and he/she is not using local server to access or view a webpage, then how allowing many features of https:// protocol to file:/// protocol as well can introduce security vulnerabilities into browsers?