Remove failing DCHECKs in Blob code.

webkit/browser/blob/blob_storage_context.cc

Index: webkit/browser/blob/blob_storage_context.cc
diff --git a/webkit/browser/blob/blob_storage_context.cc b/webkit/browser/blob/blob_storage_context.cc
index f62a26dbe545aed3ab1bd27c1d6a83096670cd7e..fe1eec368f13d7c4b493c2b9ba0c015c00447e7e 100644
--- a/webkit/browser/blob/blob_storage_context.cc
+++ b/webkit/browser/blob/blob_storage_context.cc
@@ -143,7 +143,6 @@ void BlobStorageContext::AppendBlobDataItem(
   // 4) The Blob items are expanded.
   // TODO(michaeln): Would be nice to avoid copying Data items when expanding.
 
-  DCHECK(item.length() > 0);

[michaeln, 2014/07/31 19:31:22]

These DCHECK's are here because higher level logic is expected to have filtered
out empty file and data elements before getting this far. Adding zero length
element adds nothing to the byte sequence the blob represents, so callers are
expected to weed them out so things like...

for(1 to a million) blob.add("");  // its not the real api but you get my point

... don't build big collections of nothingness.

   switch (item.type()) {
     case BlobData::Item::TYPE_BYTES:
       DCHECK(!item.offset());