The question is based on this issue in Chromium. It is marked as
Do you see any reason to block a local html file from accessing another local html file located in the same folder?
closed as off topic by maple_shaft♦ Apr 6 '12 at 1:10
Questions on Programmers Stack Exchange are expected to relate to software development within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here. If this question can be reworded to fit the rules in the help center, please edit the question.
I don't know the real answer, but here's a good guess:
It's common to use File -> Save As... to save HTML to a file. Often users will save HTML files from different web sites to the same directory (perhaps named "Downloads"). Allowing one of these files to access the other (and possibly upload it somewhere) would be a privacy leak.
Since there are more users than developers and users are less security-aware on average, protecting users probably seems more important.
Even without this feature, it's still possible to create web applications that work offline. See: http://diveintohtml5.org/offline.html
I know this is an old question, but I didn't see this important fact mentioned anywhere:
Chrome allows you to add a folder on your file system as a local Web application. Once you do that, files in that folder no longer need to be accessed through the
True, you need to write a small, three-line