Re: [w3c/FileAPI] readAsDataURL should be more precise about the data URL contents (#104)

shannonbooth left a comment (w3c/FileAPI#104)

Though, saying that - it's not clear whether the mime type should fall back to that as well for a mime type which is parsable or not.

Based on the following test, I think the logic is probably just if it is not an empty string in all browsers at least:

```js
async_test(function(testCase) {
  var blob = new Blob(["TEST"], { type: 'not a mime type' });
  var reader = new FileReader();

  reader.onload = this.step_func(function() {
    assert_equals(reader.result,
                  "data:not a mime type;base64,VEVTVA==");
    testCase.done();
  });
  reader.readAsDataURL(blob);
}, 'readAsDataURL result for Blob with unparsable MIME type');
```

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/FileAPI/issues/104#issuecomment-4209602508
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/FileAPI/issues/104/4209602508@github.com>