-
Notifications
You must be signed in to change notification settings - Fork 141
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
Update structured cloning for recent HTML changes #277
Comments
So now Should maybe make sure File API keeps that invariant alive though. |
Oh interesting. If so also let's be sure to revise the two notes in the HTML Standard about how URL parsing uses StructuredSerialize. |
So as long as blob URLs also work for MediaStream and MediaSource this is not going to work, since those two objects are mutable. |
However, those two objects cannot be serialized/deserialized (though MediaStream can be cloned through a locally defined operation). Good times. Per w3c/mediacapture-main#404 blob URLs might go away for MediaStream. I guess we should just accept that those objects are mutable and what you get depends on when you start reading them... |
It was wrong for MediaSource and MediaStream objects, which cannot be serialized and deserialized, and it’s no longer necessary for Blob objects as their state cannot be modified. (And it’s also out-of-date as HTML now has serialization and deserialization operations.) Fixes #277.
As per whatwg/url#277 it cannot and does not need to use StructuredSerialize.
As per whatwg/url#277 it cannot and does not need to use StructuredSerialize.
It was wrong for MediaSource and MediaStream objects, which cannot be serialized and deserialized, and it’s no longer necessary for Blob objects as their state cannot be modified. (And it’s also out-of-date as HTML now has serialization and deserialization operations.) Fixes #277.
As per whatwg/url#277 it cannot and does not need to use StructuredSerialize.
whatwg/html@97d644c changed structured cloning significantly. I am not sure what the correct changes are here myself; it will likely require coordination with the File API folks.
The text was updated successfully, but these errors were encountered: