-
Notifications
You must be signed in to change notification settings - Fork 312
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
Remove StructuredCloneWithTransfer and add a messageerror event #1116
Labels
Comments
domenic
added a commit
to domenic/ServiceWorker
that referenced
this issue
Apr 20, 2017
This is part of whatwg/html#2530; see related links there for more information. Closes w3c#1116.
domenic
added a commit
to domenic/ServiceWorker
that referenced
this issue
Apr 20, 2017
This is part of whatwg/html#2530; see related links there for more information. Closes w3c#1116.
annevk
added a commit
to whatwg/html
that referenced
this issue
Apr 24, 2017
The messageerror event is used when deserialization fails. E.g., when an ArrayBuffer object cannot be allocated. This also removes StructuredCloneWithTransfer as deserializing errors now need to be handled on their own. Tests: web-platform-tests/wpt#5567. Service workers follow-up: w3c/ServiceWorker#1116. Fixes part of #2260 and fixes #935.
domenic
pushed a commit
to whatwg/html
that referenced
this issue
Apr 24, 2017
The messageerror event is used when deserialization fails. E.g., when an ArrayBuffer object cannot be allocated. This also removes StructuredCloneWithTransfer as deserializing errors now need to be handled on their own. Tests: web-platform-tests/wpt#5567. Service workers follow-up: w3c/ServiceWorker#1116. Fixes part of #2260 and fixes #935.
domenic
added a commit
to domenic/ServiceWorker
that referenced
this issue
Apr 24, 2017
This is part of whatwg/html#2530; see related links there for more information. Closes w3c#1116. Also makes some minor updates to stop referencing terms that have been removed from HTML.
domenic
added a commit
to domenic/ServiceWorker
that referenced
this issue
Apr 28, 2017
This is part of whatwg/html#2530; see related links there for more information. Closes w3c#1116. Also makes some minor updates to stop referencing terms that have been removed from HTML.
jungkees
pushed a commit
that referenced
this issue
Apr 29, 2017
This is part of whatwg/html#2530; see related links there for more information. Closes #1116. Also makes some minor updates to stop referencing terms that have been removed from HTML.
inikulin
pushed a commit
to HTMLParseErrorWG/html
that referenced
this issue
May 9, 2017
The messageerror event is used when deserialization fails. E.g., when an ArrayBuffer object cannot be allocated. This also removes StructuredCloneWithTransfer as deserializing errors now need to be handled on their own. Tests: web-platform-tests/wpt#5567. Service workers follow-up: w3c/ServiceWorker#1116. Fixes part of whatwg#2260 and fixes whatwg#935.
inikulin
pushed a commit
to HTMLParseErrorWG/html
that referenced
this issue
May 9, 2017
The messageerror event is used when deserialization fails. E.g., when an ArrayBuffer object cannot be allocated. This also removes StructuredCloneWithTransfer as deserializing errors now need to be handled on their own. Tests: web-platform-tests/wpt#5567. Service workers follow-up: w3c/ServiceWorker#1116. Fixes part of whatwg#2260 and fixes whatwg#935.
alice
pushed a commit
to alice/html
that referenced
this issue
Jan 8, 2019
The messageerror event is used when deserialization fails. E.g., when an ArrayBuffer object cannot be allocated. This also removes StructuredCloneWithTransfer as deserializing errors now need to be handled on their own. Tests: web-platform-tests/wpt#5567. Service workers follow-up: w3c/ServiceWorker#1116. Fixes part of whatwg#2260 and fixes whatwg#935.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Apologies for the churn. For SharedArrayBuffer we need to tweak serializing and deserializing a little further and unfortunately service worker is affected as well (you might have noticed another issue related to this as well and there might be some more coming).
whatwg/html#2530 has the change to HTML and service workers will need to do something similar. Use StructuredSerializeWithTransfer and StructuredDeserializeWithTransfer separately and give each their own error handling.
The text was updated successfully, but these errors were encountered: