Skip to content
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

Define storage operation of non-trivial StructuredSerializeForStorage records (e.g. Blob/File) #203

Closed
inexorabletash opened this issue May 12, 2017 · 2 comments
Labels

Comments

@inexorabletash
Copy link
Member

Forked from #170

HTML's StructuredSerializeForStorage outputs "records" which are mostly plain-old-data but occasionally not, e.g. File and Blob.

@annevk points out over yonder:

... I think it's not quite an implementation-detail for File, Blob, and SharedArrayBuffer objects. E.g., does File continue to be a pointer or do we make a copy ...

(Note that we throw for SABs so that's not an issue)

I need to wrap my head around what's not covered by the monkey patching details.

(Since we're already a good bit more rigorous than "v1" I'm not considering this a blocker for "v2" for those who prefer versioned specs.)

@annevk
Copy link
Member

annevk commented Feb 26, 2018

This seems more like an issue for the File API, no?

@inexorabletash
Copy link
Member Author

Yeah. I'll close this out.

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

No branches or pull requests

2 participants