[Webkit-unassigned] [Bug 89034] [Chromium] reading Blob includes non-existent file doesn't throw NotFound error

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed Jun 13 22:47:56 PDT 2012


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





--- Comment #4 from Kinuko Yasuda <kinuko at chromium.org>  2012-06-13 22:47:56 PST ---
(In reply to comment #3)
> (In reply to comment #2)
> > > I don't think we need to fix this; fixing #1 will resolve the user-visible issues,
> > 
> > Note that we'll still have tiny incompatibility when we add an empty file and then the file gets removed before reading though it'll hardly be a real problem.
> 
> I think we'll still match, actually.  If we snapshot before it's removed, we'll know it's zero length, and then not try to read from it.  I expect other ports to do the same--why try to read zero bytes?

Yup, though it doesn't seem to be spec'ed?  Maybe we could file a w3c bug?  How other browsers work?

When one uploads multiple files including empty one, the server may get different set of files unless it's cleared?

-- 
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