[WASM] CR transition for WebAssembly JavaScript Interface #137
Labels
Awaiting Publication
Approved by the Director, waiting on publication
Awaiting Team Contact
Entering CR
First Candidate Recommendation
wg:wasm
Document title, URIs, estimated publication date
target: https://www.w3.org/TR/2019/CR-wasm-js-api-1-20190516/
source: http://webassembly.github.io/spec/js-api/
to be published with: to be published with: Core and WebAPI
Abstract
This document provides an explicit JavaScript API for interacting with WebAssembly.
Part of a collection of related documents: the Core WebAssembly Specification, the WebAssembly JS Interface, and the WebAssembly Web API.
Status
Standard bikeshed SOTD plus advice that the following issue may change implementations:
[[
#985. [js-api] Review object caching (Mar 14, 2019)
postMessage re-uses existing objects so as not to not grow memory
]]
Decision to request transition
https://github.com/WebAssembly/meetings/blob/master/2019/WG-02-13.md#--request-that-we-move-forward-with-a-candidate-recommendation-cr
Changes
Requirements satisfied
N/A
Dependencies met
Some changes to WebAssembly core.
Wide Review
Reviewed with WebAssembly core specification, see list in #119.
Issues Addressed
Issues are addressed on http://github.com/WebAssembly/spec. See, for example, the following issues related to this specification:
Open issues:
#810. js api: improve definition of error objects (editorial)
#741. [js-api] Allow optional asynchronous steps after instantiation? (awaiting close by commenter)
Formal Objections
None.
Implementation
See results for 4 implementations at https://wpt.fyi/results/wasm/jsapi.
*.any.js
failures are an infrastructure bug.grow.any.*
failure includes a test for a future feature which is not yet enabled by default.Patent disclosures
https://www.w3.org/2004/01/pp-impl/101196/status#current-disclosures
The text was updated successfully, but these errors were encountered: