This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24469 - Definition of "valid blob" is unclear and probably wrong
Summary: Definition of "valid blob" is unclear and probably wrong
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: File API (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Arun
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
: 24573 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-02-02 12:59 UTC by Ms2ger
Modified: 2014-02-27 22:29 UTC (History)
3 users (show)

See Also:

Attachments

Description Ms2ger 2014-02-02 12:59:42 UTC 
http://dev.w3.org/2006/webapi/FileAPI/#validBlob states:

> a valid blob argument, which is a non-null Blob in scope of the
> global object's URL property from which this static method is called

I have no idea what that means. The one thing I could imagine—that the methods should not work for Blobs created in another global scope—is not implemented by either Gecko or Chrome, and I don't see why it would.

Also note that neither method takes a nullable blob, so "non-null" is pointless at best.
Comment 1 Simon Pieters 2014-02-07 09:45:35 UTC 
*** Bug 24573 has been marked as a duplicate of this bug. ***
Comment 2 Arun 2014-02-27 22:29:06 UTC 
Fixed; this concept doesn't exist anymore, but closed blobs have been defined more clearly.