[Webkit-unassigned] [Bug 89034] New: [Chromium/Blob]

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=89034

           Summary: [Chromium/Blob]
           Product: WebKit
           Version: 528+ (Nightly build)
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: HTML DOM
        AssignedTo: webkit-unassigned at lists.webkit.org
        ReportedBy: ericu at chromium.org
                CC: kinuko at chromium.org


Chromium's Blob/BlobBuilder implementation now has a couple of behaviors that diverge from either the spec or the WebCore implementation or both.

1) [Likely spec divergence, but we match WebCore]: We don't snapshot a File at creation time.  We wait until the File is sliced or added to another Blob to capture its size and modification date.  This bug report is NOT for this spec divergence, but you have to know about this to understand that:
2) In Chromium, if you try to add a zero-length File or Blob [including a File with no backing file] to a Blob or BlobBuilder, we just silently drop it.  If it's a valid zero-length Blob or File, this isn't a problem.  However, if it's an invalid File [whose backing file is missing], we'd ideally generate an error somewhere along the line.  In the old code [before a couple of weeks ago] we'd just add it, and only find out at read time that there was a problem, and throw a read error.  This matched WebCore behavior.  When we fix #1, we'll find out at File creation time, and throw an error then.  In our current state, there's no error at all.

I don't think we need to fix this; fixing #1 will resolve the user-visible issues, since we'll then do no file IO at slice/add-Blob time and thus not notice an error or drop the File then.  But this bug is here to track the fact that we're currently showing the wrong behavior and failing silently.

There's a Chromium bug for #1 already: http://code.google.com/p/chromium/issues/detail?id=129325; we may need a WebKit bug as well.

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