Comments (4)
I think the difference would be that with the sync constructors you wouldn't know if construction failed; you'd only get an error as soon as something tries to read from the blob (that's already how it works today in chrome; blob construction can already fail). While with these async factories you could detect and handle these errors sooner. While I agree that most developers probably wouldn't care/bother, it does seem like some subset of developers would probably like to be able to detect these kinds of errors.
from fileapi.
I'm confused. Why would web developers ever use these async factories instead of using the existing sync ones?
from fileapi.
Are these kind of blobs you cannot read from defined properly? Does their existence mean we could bring back close()
and some kind of promise-returning status getter?
from fileapi.
#154 is trying to define "blobs you can't read from" properly. Although not specifically these blobs. Some kind of status getter might make sense (especially for things like IDB, file and cache storage backed blobs that can start out readable, and later become unreadable). Not sure about close; or at least close with any guarantees on effects on quota, memory usage etc.
from fileapi.
Related Issues (20)
- TPAC planning and specification status report HOT 2
- Support using AbortController with FileAPI HOT 6
- Specify how filenames from the OS map to File's `name` property HOT 2
- features request:add SynFileReader for Avoid Callback Hell Programming from FileReader HOT 1
- Clarify UUID version HOT 1
- Align with ReadableStream changes HOT 1
- Issues with MIME types HOT 2
- Consider allowing re-reads after snapshot state change for applications loaded from file: URIs
- Disparity in `loadend` event dispatch between spec, implementation & tests HOT 4
- blob: slice() without valid content type yields unexpected results HOT 2
- TPAC 2022 status report HOT 1
- Consider adding `blob.dataUrl()` method, or some other analogue to `readAsDataURL` HOT 9
- Broken references in File API
- Byte stream support for `stream()`?
- Function signature change: reading all bytes from a stream
- createObjectURL with ReadableStream HOT 2
- Don't export "resolve" HOT 4
- Proposal: Add a capability to create a Blob URL with a unique (non-opaque) origin HOT 19
- Specify actual byte reading algorithm for Blob.stream()
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from fileapi.