Skip to content

Spec mostly doesn't mention blob expectations #454

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
evanstade opened this issue May 2, 2025 · 1 comment
Open

Spec mostly doesn't mention blob expectations #454

evanstade opened this issue May 2, 2025 · 1 comment

Comments

@evanstade
Copy link
Contributor

evanstade commented May 2, 2025

We expect that blob handle can outlive the records and databases they are (were) stored in, but that's not mentioned anywhere in the spec.

This Chromium implementation doc may be helpful.

This does already have WPT coverage.

@mkruisselbrink
Copy link

This is something I've been meaning to address from the FileAPI side as well (which currently more or less pretends that a Blob is an immutable bunch of bytes, and as such will always remain valid after it has been created). Without actually making things more rigorous on that side, probably specifying what the "snapshot state" of a IndexedDB backed blob is is the best you can do (similar to how it's kind of hand-wavy described for file backed blobs)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants