On 10/10/17 5:25 AM, Simon Sapin wrote:
(By the way, to do we disallow access to file: from http: and other URL
schemes?)
We do not have any special checks for it beyond regular cross-origin ones.
___
dev-servo mailing list
dev-servo@lists.mozilla.org
`grep -r std::fs components` returns many results:
components/net/hosts.rs:use std::fs::File;
components/net/filemanager_thread.rs:use std::fs::File;
components/net/resource_thread.rs:use std::fs::File;
components/net/image_cache.rs:use std::fs::File;
components/net/fetch/methods.rs:use std::fs::F
On 10/10/2017 10:34, Paul Rouget wrote:
Does it make sense to make it so that Servo does do any disk IO and
delegate everything to the embedder?
For example, on Android, reading the resources file is hacky because
we have to copy the files at startup to the sdcard.
Not because we can't have reso
Does it make sense to make it so that Servo does do any disk IO and
delegate everything to the embedder?
For example, on Android, reading the resources file is hacky because
we have to copy the files at startup to the sdcard.
Not because we can't have resources files in the apk, but because
servo
4 matches
Mail list logo
