[Webkit-unassigned] [Bug 78648] FileReader is dysfunctional in documents with "null" origin string

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 14 16:44:21 PST 2012


--- Comment #1 from Jian Li <jianli at chromium.org>  2012-02-14 16:44:21 PST ---
(In reply to comment #0)
> FileReader doesn't work in documents with unique security origin, or in file documents when file path separation is enforced. The reason is that:
> 1. Origin string for such is null.
> 2. FileReaderLoader::start tries to create a blob URL.
> 3. BlobURL::createBlobURL bails out when it sees a "null" origin string.
> As an example of configuration where this is broken, try opening any FileReader regression test from fast/files in Google Chrome.
> Why does FileReader need a blob URL to read a file, in the first place?

This is because we want to share the same code for both file/blob reading and blob URL request fetching in multi-process environment. When a file/blob is created for the first time, it is identified by an internal used blob URL, that can allow it to be read by either FileReader or blob URL request.

Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

More information about the webkit-unassigned mailing list